-
Notifications
You must be signed in to change notification settings - Fork 89
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
Add Support for Symfony 6 #736
Conversation
9f5e2f3
to
58aa0a9
Compare
.github/workflows/build.yml
Outdated
php: [8.0, 8.1] | ||
node: [10.x] | ||
mysql: [5.7, 8.0] | ||
symfony: [^4.4, ~5.2.0, ~5.3.0] |
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.
I think I told you about it already that it is IMO a good idea to drop SF 4.4 in a separate PR. But if you want to keep it as it is, let's add it at least to the PR title to have this info in the generated changelog on next release 😀
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.
9102c29
to
f6a6153
Compare
...s/Expected/address_book/SF6/validation_create_address_book_with_wrong_province_response.json
Outdated
Show resolved
Hide resolved
...es/Expected/address_book/SF6/validation_create_address_book_with_wrong_country_response.json
Outdated
Show resolved
Hide resolved
if (Kernel::VERSION_ID < 60000) { | ||
$this->assertResponse($response, 'address_book/SF5/validation_create_address_book_with_wrong_country_response', Response::HTTP_BAD_REQUEST); | ||
} else { | ||
$this->assertResponse($response, 'address_book/SF6/validation_create_address_book_with_wrong_country_response', Response::HTTP_BAD_REQUEST); | ||
} |
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.
To avoid that, we could probably define the custom validation message
Thanks, Kamil! 🎉 |
continuation of / to potential merge after merging #734