-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
8000
(Translation) Add notice if to be translated entity is not found #3015
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
Labels
Comments
It's not an issue, it's a feature request. Address it to the user group or development group for a clue. Quickly, you need to override the translator class to add the custom translation method. |
Working on PR (guess since this ticket is listed in the blog post, the basic idea is accepted) |
@meandmymonkey what about the PR ? |
Will probably take until end of the week. |
fabp
7279
ot
added a commit
that referenced
this issue
Sep 24, 2014
This PR was squashed before being merged into the 2.6-dev branch (closes #10887). Discussion ---------- [Translation] added LoggingTranslator. | Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #3015, #2435 | License | MIT | Doc PR | symfony/symfony-docs/pull/4050 Commits ------- b7770bc [Translation] added LoggingTranslator.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I would like to have (a configurable?) feature where trying to translate something via the translator that does not exist for the current language result in a warning or notice in the log files.
Sometimes a translation slip through because of typos and it would be handy if I could see all the missed ones in the log when used.
Thanks
The text was updated successfully, but these errors were encountered: