-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Translation] translation:debug for views in app/ folder #12273
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
Comments
@sebastianblum thanks for reporting this error! It's true that the current I wonder if there is an easy way to update the command to allow scanning templates in any given directory and without breaking BC (or without breaking BC too much). |
s/bergmann/blum/ ;-) |
IMO, translation:debug would be better based on the domain rather than the bundle. The translator does not distinguish translations per bundle but per domain |
…tion debugging in directories (xelaris) This PR was merged into the 2.7 branch. Discussion ---------- [Translation][Command][FrameworkBundle] Enable translation debugging in directories | Q | A | ------------- | --- | Bug fix? | no | New feature? | yes | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #12273 | License | MIT | Doc PR | This PR follows up #13340 and enables not only to inspect Bundles, but also directories, like the `app/` directory. Additionally it harmonizes the TranslationDebugCommand and TranslationUpdateCommand to expect an optional bundle name or a directory and fall back to kernel root dir if none of them is given. Commits ------- 2662244 [FrameworkBundle] Enable translation debugging in directories
In the symfony best-practices, it is recommended, that the templates are stored in app/views/ (page 26).
But at the moment, it is not possible to debug the translation files
doesn't find templates in the app/views/ folder.
The text was updated successfully, but these errors were encountered: