-
Notifications
You must be signed in to change notification settings - Fork 7
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
filters for arrays #45
Conversation
@regiscamimura what's happening here? |
The previous version of the ListAPI would support array parameters like |
Alright, cool, it might be worth doing something like this instead so we're not string building just for self.q_objects.add(Q(**{f"{key}__in": self.bundle[key]}), Q.AND) I copied this from the search fields stuff above and maybe it's not quite right; but generally any approach where we apply the Might be worth checking over line 84-90 while you're here if you have a moment, because they don't look right, is |
Why should we preserve the
|
I realize that we parsing and then === Preserve the format because it complies with usual query string format for multiple parameters, syntax sugar and such. Besides, it would be an update that doesn't breaks current applications (you know which) using the framework. |
refs #48 |
That’s the format that axios will use when you pass an arrays of things in, my preference is we don’t support commas, it has just come for free in django url filter. |
No description provided.