Skip to content

explain precedence of translation directories #13430

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 9, 2020
Merged

explain precedence of translation directories #13430

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion reference/configuration/framework.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2186,7 +2186,9 @@ paths
**type**: ``array`` **default**: ``[]``

This option allows to define an array of paths where the component will look
for translation files.
for translation files. Translation entries from later directories overwrite
earlyer ones. The last processed dir is `default_path <reference-translator-default_path>`
(which has a default value).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This order is the result of my tests. Could somebody confirm please?

In case you do not use flex: app/Resources/translations is after default_path.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's correct.


.. _reference-translator-default_path:

Expand Down