-
Notifications
You must be signed in to change notification settings - Fork 292
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
Use choice translation domain #419
base: master
Are you sure you want to change the base?
Use choice translation domain #419
Conversation
Wasn't sure if this qualifies as BC break since extractor previously didn't take into account choice_translation_domain which will cause translations to be extracted under different (correct) domain now. Also will correctly skip translations with |
de3b1f7
to
7dce4f0
Compare
When it becomes available this feature? I hope soon... |
the other issue with this change is that the choice_translation_domain doesn't exist as a valid option for sf 2.3 which for whatever reason this bundle still supports even though 2.3 is no longer supported. We would have to drop support for sf2.3 with this. |
I don't think we need to drop the support for 2.3. The translation domain falls back to previous behaviour of using |
Well the tests will be trying to pass an option that doesn't exist in 2.3. So if we don't drop 2.3 support we need to then only conditionally run those tests when sf is > 2.3. |
I don't think test forms are actually executed so it shouldn't matter. And if users try to use the option on the forms, Symfony will inform them that the option doesn't exist. |
Can you rebase this on master please? |
7dce4f0
to
fdc8f32
Compare
Done :) |
Can you review the test failures and see if you can fix/determine the issue? |
fdc8f32
to
c2e3854
Compare
Updated tests and rebased. No idea why that one test is failing though. |
This is a very old pull request but it has some important improvements that can be considered. For example, it seems like in the current version the translation_domain and choice_translation_domain when set to false still trigger the extraction. This is in conflict with Symfony's document which clearly states that false mean no translation. |
5ff05e2
to
2aa7af9
Compare
Rebased against latest develop |
Description
Considers choice translation domain when extracting translation strings. Also ignores translates that have
false
as translation domain.Todos