Uh oh!
There was an error while loading. Please reload this page.
feat: not equal range filter - #4746
Conversation
Co-Authored-By: Samuel Chiriluta <3427855+samuel4x4@users.noreply.github.com>
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. |
divine
commented
Nov 7, 2022
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. |
divine
commented
Jan 13, 2023
Not stale.... |
@divine actually I'm wondering if |
nesl247
commented
Sep 8, 2023
Agreed. This belongs to the should probably work. I ported the changes we did for our own explicit |
divine
commented
Sep 14, 2023
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! |
VincentLanglet
commented
Jan 25, 2026
To me this using it this way would be a hacky undocumented feature with no BC promise. At first I thought that the NotEqual type didn't make sens in a range filter but that could be considered as a range Are you still interested by this PR @divine ? If yes could you solve the conflict ? Thanks |
soyuka
commented
Jan 26, 2026
@VincentLanglet this is part of the work around the range refactoring #4689 |
VincentLanglet
commented
Jan 26, 2026
I'm not sure to understand ; the #4689 PR is talking about UuidRangeFilter, this does not seems incompatible with the fact to add a "Not equal range" filter. Which seems a easier PR/step to finish than the big refacto of #4689. |
This is a follow-up for #4546 with the added test.