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
Remove reverse fields #579
Conversation
098434f
to
b13722e
Compare
Happy we can leave these reverse fields behind they were just noise in the code for the most part |
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.
🥇
But lets test it in this PR before we merge it. Was the import already triggered?
Yes |
Ignore my comment above. I didn't see you've already tested this. |
Their initial purpose was suffix queries, but this should be handled by the wildcard queries now.
This is mostly dead code after removing reverse fields, since the `query` function was only used by the `Reversable` implementation. This should be handled by wildcard queries anyway.
b13722e
to
41c0827
Compare
Triggered an import, will merge when it's done |
Their initial purpose was suffix queries, but this should be handled by the wildcard queries now.