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
Fix Issue #875 #974
Fix Issue #875 #974
Conversation
Is it good approach - to hardcode locale? 🤔 Probably, it's better to use dotenv and set LC_ALL to "en_US.UTF8", "de_DE.UTF8", etc. Doing so we can test localized messages by equivalence classes. Edit: fix typo. |
Hardcoding because we're using en-US.UTF8 formatting for numerical displays. Not sure what would be the need for setting de_DE.UTF8 or any other local format, it'd just fail the test. Unless we're localizing the whole app to account for different formats 🤷 |
I think this is going to make people in non en-us countries very unhappy. What if we just make the test use |
good point! updated - tests now use |
Looks good, will merge if tests pass. |
@NullSoldier updated fix for lint issues. |
Can you base this off staging? |
- need to use toLocaleString() in currency display tests. otherwise we'll run in to localization errors.
61adf81
to
5cbefb7
Compare
yes sir |
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.
Looks good, thank you!
Localization error is causing languages that use
,
instead of.
to break (ie de_DE). Applying "en-US" in toLocaleString() to prevent this error.