-
-
Notifications
You must be signed in to change notification settings - Fork 175
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
Laravel 5.4 Fixes with Tests #224
Conversation
@torrentalle Can you review this, please? |
Not sure if it's working on older Laravel versions but it seems to work in 5.4 |
@torrentalle Would love to see this merged into the project soon! 🙏 |
@torrentalle bumpity =) |
Been waiting since a week sadly 😞 |
OK. The pull request is accepted. |
Whoah! =) Thanks @drjoju |
This PR not working for me:
I'm using Laravel 5.4.24 |
@kamrava you need to update the package from stable version(1.5.0) to dev-master |
@a-komarev how come Laravel make such changes in a minor version that break everything backward? |
@akkhan20 Laravel don't follow SemVer standard. Laravel 5.1 > 5.2 means something similar like 1.0 > 2.0 in SemVer. |
I've updated the code and the tests to work with Laravel 5.4 and thus created breaking changes against previous versions. I wasn't sure what to do with your testing setup as there are multiple
composer.json
's for the different Laravel versions to be tested. But these don't seem to be needed anymore as the code changes I've done will break on previous Laravel versions.I've had to create a proxy class for the
ValidationRuleParser
because its parse function is static and it didn't seem like you could mock static functions. I've done this to allow theDelegatedValidator
to be tested. Annoyingly it will be the only class in your code base not being tested, so interested in what your thoughts are.Thanks
Chris