Skip to content

Conversation

@WebVPF
Copy link
Contributor

@WebVPF WebVPF commented Jan 15, 2022

No description provided.

Copy link
Member

@LukeTowers LukeTowers left a 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.

@WebVPF
Copy link
Contributor Author

WebVPF commented Jan 15, 2022

Please also review all of the changed files to ensure that the Lang facade is imported correctly for each one.

@LukeTowers
done

@bennothommo
Copy link
Member

@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.

@LukeTowers
Copy link
Member

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.

@WebVPF
Copy link
Contributor Author

WebVPF commented Nov 30, 2022

@LukeTowers I removed the translation of system exceptions.

@LukeTowers
Copy link
Member

@bennothommo tests are failing, is that because of the classloader changes?

@bennothommo
Copy link
Member

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants