fix: locales like 'pt_BR' 'fr_BE' will work when send to the frontend #402
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I recently had a problem using laravel-file-maneger. When I opened the manager it didnt show any file, only folder. Trying to find the problem I found the following error in the frontend:
So looking more deep I found the problem is the same as here: formatjs/formatjs#2440
Basically, if you use intl for internationalization, it wont work if it couldnt find a valid lang for the case, so, 'pt_BR' is a invalid lang, but 'pt-BR' is valid.
But why dont I change that in the app.php config?
Because php use the oposite 😃.
You can see here: https://www.php.net/manual/en/intlcalendar.getavailablelocales.php
So, this PR only replace all
_in a locale with-. I checked and any Intl locales use '_' in their names.