-
-
Notifications
You must be signed in to change notification settings - Fork 927
feat: not equal range filter #4746
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
Co-Authored-By: Samuel Chiriluta <[email protected]>
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale... |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale.... |
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.
LGTM 👌
@divine actually I'm wondering if |
Agreed. This belongs to the
should probably work. I ported the changes we did for our own explicit |
Hello, I can't entirely agree if this should be in core/src/Doctrine/Common/Filter/RangeFilterInterface.php Lines 22 to 29 in d85884d
"ne" is better sits in Rangefilter IMO even though it doesn't look right until you see the parameter names in both files. core/src/Doctrine/Common/Filter/SearchFilterInterface.php Lines 22 to 48 in d85884d
I'm not the person to decide so let's give a voice from @api-platform/core team. Thanks! |
This is a follow-up for #4546 with the added test.