-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make configurable callback exceptions #189
Labels
Comments
If you accept this suggestion and a PR is needed or wanted, I can do it. |
@rafa-as sorry for the delay, had busy times. feel free to fire a PR and i'll approve. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a ... (check one with "x")
Current behavior
Currently only two metas has the "exception" status, 'og:locale' and 'og:locale:alternate'
Expected/desired behavior
Configure the callback exceptions.
What is the motivation / use case for changing the behavior?
It's impossible or undesired, suppose or predict the metas that the projects wants to exclude from callback function. In our case, we have for example 'og:type' or 'og:image' that doesn't need translation (thought the callback function).
The workaround for this situation in our case it's the next:
The text was updated successfully, but these errors were encountered: