Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Form] Add intl/choice_translation_locale option to TimezoneType#31294
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
yceruto left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
The Form part LGTM.
This PR was merged into the 4.3 branch.Discussion---------- [Intl] Revise timezone name generation| Q | A| ------------- | ---| Branch? | master| Bug fix? | yes| New feature? | no| BC breaks? | no <!-- seehttps://symfony.com/bc -->| Deprecations? | no| Tests pass? | yes (inlcluding intl-data group)| Fixed tickets | #... <!-- #-prefixed issue number(s), if any -->| License | MIT| Doc PR | symfony/symfony-docs#... <!-- required for new features -->This is the final polishing needed for#31294 :)I've realized it's much easier to de-duplicate by processing fallback locales separate, and then only keep the diff compared to a specific locale. More or less the same approach `LocaleDataGenerator` already follows. I was trying to be clever and filter based on inheritance in a single process; bad idea.Includesro0NL@31591d0 (ref#31432)Commits-------bfdb4ed [Intl] Revise timezone name generation
nicolas-grekas commentedMay 9, 2019
Time for rebase. |
ro0NL commentedMay 9, 2019 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
4.3? would makes sense as we added all the timezone related infra in 4.3 already, which purpose it was to support this feature 😅 |
ro0NL commentedMay 9, 2019
Figured it out, locally i invoked testing the whole suite, shows we have a global state issue with the default locale. Last commit should do, not sure why it starts failing now, as other intl types have the same test :/ |
...ponent/Form/Tests/Extension/Core/DataTransformer/IntegerToLocalizedStringTransformerTest.php OutdatedShow resolvedHide resolved
Uh oh!
There was an error while loading.Please reload this page.
This PR was merged into the 3.4 branch.Discussion----------[Form] Restore default locale during tests| Q | A| ------------- | ---| Branch? | 3.4| Bug fix? | yes-ish| New feature? | no| BC breaks? | no <!-- seehttps://symfony.com/bc -->| Deprecations? | no| Tests pass? | yes <!-- please add some, will be required by reviewers -->| Fixed tickets |#31294 (comment)| License | MIT| Doc PR | symfony/symfony-docs#... <!-- required for new features -->This fixes the failing tests in#31294Commits-------7fce86f [Form] Restore default locale during tests
ro0NL commentedMay 10, 2019
All good (failures unrelated) |
fabpot commentedMay 13, 2019
Thank you@ro0NL. |
…mezoneType (ro0NL)This PR was merged into the 4.3 branch.Discussion----------[Form] Add intl/choice_translation_locale option to TimezoneType| Q | A| ------------- | ---| Branch? | master| Bug fix? | no| New feature? | yes| BC breaks? | no <!-- seehttps://symfony.com/bc -->| Deprecations? | no| Tests pass? | yes <!-- please add some, will be required by reviewers -->| Fixed tickets |#28836| License | MIT| Doc PR |symfony/symfony-docs#11503final step :)for now i think any form of grouping is a user concern (i.e. by GMT offset or area name); see#31293 +#31295having a special built in `group_by' => 'gmt_offset'` util would be nice, and can be done in the future.includes#31434Commits-------001b930 [Form] Add intl/choice_translation_locale option to TimezoneType
Uh oh!
There was an error while loading.Please reload this page.
final step :)
for now i think any form of grouping is a user concern (i.e. by GMT offset or area name); see#31293 +#31295
having a special built in
group_by' => 'gmt_offset'util would be nice, and can be done in the future.includes#31434