-
-
Notifications
You must be signed in to change notification settings - Fork 15
localization of error messages #23
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
base: main
Are you sure you want to change the base?
Conversation
LukeTowers
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.
Please also review all of the changed files to ensure that the Lang facade is imported correctly for each one.
@LukeTowers |
|
@WebVPF @LukeTowers this appears to break the unit tests since they are doing string comparisons on some exceptions. Also, I believe our standard is to not translate system exceptions. |
|
At least some of these are application exceptions though and are triggered by the user entering data which probably should be translated. System exceptions designed to be searched online shouldn't be translated but exceptions that are meant to inform the user how to solve their problem with the message itself can be translated. |
|
@LukeTowers I removed the translation of system exceptions. |
|
@bennothommo tests are failing, is that because of the classloader changes? |
|
@LukeTowers not quite sure what's happening there - the Backend module classes are using Composer's PSR-4 autloading, so I don't think it would have anything to do with the class loader changes. I also just did a simulation of the same thing the tests do, and the tests ran fine for me. |
No description provided.