-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Intl component - missing region #47825
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
see #31365 which was ultimately caused by https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Exceptional_reservations |
yes. Do you experience it as a bug? |
Well it's causing an error as there is data saved against that code which no longer exists. My thoughts would be that getName should still fallback to the full list when performing a lookup. |
ideally we preserve BC by deprecating removed entries first, but that's a data issue which isnt nessecarily covered by the current BC promise AFAIK 😅
nope :)
so anticipating it seems best |
Hey, thanks for your report! |
Friendly ping? Should this still be open? I will close if I don't hear anything. |
Hey, I didn't hear anything so I'm going to close it. Feel free to comment if this is still relevant, I can always reopen! |
Symfony version(s) affected
6.*
Description
I have a application which was recently upgraded from Symfony 3.4 to 6 and I have noticed that there is a region missing from the Intl component.
The region that I have found was "AC" - https://github.com/symfony/intl/blob/3.4/Resources/data/regions/en.json#L3
Within the application, we have the following method:
However, this now throws a
Symfony\Component\Intl\Exception\MissingResourceException
exception.The only option for us is to catch this exception and return the code instead:
It seems odd that this region has disappeared when it still exists here: https://www.iso.org/obp/ui/#iso:code:3166:AC
How to reproduce
Possible Solution
Load "AC" and any other missing regions back into the Intl php arrays. Unless this was intentionally removed?
Additional Context
No response
The text was updated successfully, but these errors were encountered: