-
-
Notifications
You must be signed in to change notification settings - Fork 344
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 composite primary keys tests and use Paginator #1268
Add composite primary keys tests and use Paginator #1268
Conversation
5079f99
to
5b5b735
Compare
1603c5f
to
81b5038
Compare
3c12b79
to
b46be01
Compare
If I had understood correctly #1217 (comment), the problem is when the composite keys are relations, with scalar values should work fine, can you please add a test with relations? |
fee066b
to
af7566c
Compare
af7566c
to
a80db5e
Compare
Done @franmomu :) |
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 these tests are fine.
I just have a concern about using real trademarks in the fixtures. I think we should avoid them if possible.
I removed the trademarkes @phansys |
I added some functional tests for composite primary keys.
https://github.com/sonata-project/SonataDoctrineORMAdminBundle/pull/1268/checks?check_run_id=1717007313 show the failure if I removed the code for composite keys.
Then I added the PR #1217, to check that the code is still working fine.
Changelog