-
Notifications
You must be signed in to change notification settings - Fork 772
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
Move filter options to Meta class #459
Move filter options to Meta class #459
Conversation
@carltongibson - btw, this is also ready for review. |
Sweet. I will rebase the other PRs later tonight* *probably |
This causes an error with rest_framework_gis, which tries to update the I've only skimmed this, but it looks like handling this was not taken from #429? |
Well #429 is incoming, but the Exactly what are you referring to by "this" and "it" in "handling this" and "Is it planned"? (again I'm not quite following you immediately) |
Sorry, I've meant to ask if it would work after #429, but only issue a deprecation warning (according to https://github.com/carltongibson/django-filter/pull/429/files#diff-c82ea95d2a317d98860bf154f27d3e17R181). And since this could have been done in this PR (#459) already, I've thought that it might have slipped through.
But it should not throw an error, but only warn about the deprecation, right? |
It's reference semantics, so it should be fine yes. I think :-) |
This will only work if class MyFilterSet(GeoFilterSet):
filter_overrides = {}
... If you omit the attribute, there is no Also, the correct thing for rest_framework_gis to do after #429 merges is to copy & update the class |
Thanks for your clarification, @rpkilby. |
The breakage is covered by the 0.x already. I want to make the 1.0 after removing all the deprecations. |
Extracted the
strict
,filter_overrides
, andorder_by_field
moves toMeta
from the other PRs. This resolves #430.