-
-
Notifications
You must be signed in to change notification settings - Fork 158
Support custom filter strategy #186
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
Labels
Comments
I agree that this is an area where we need to be more flexible. What I would like to see happen is the parsing logic moved out of |
jaredcnance
added a commit
that referenced
this issue
Nov 13, 2017
jaredcnance
added a commit
that referenced
this issue
Nov 13, 2017
…ility * chore(csproj): bump package version * refactor(query-set): move logic into IQueryParser to improve extensibility closes #186
jaredcnance
added a commit
that referenced
this issue
Aug 12, 2018
…ility * chore(csproj): bump package version * refactor(query-set): move logic into IQueryParser to improve extensibility closes #186
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Filtering is not really specified in the jsonapi.org specification and we have actually chosen an other filter strategy than is implemented in JsonApiDotNetCore.
Would it be possible/desirable to make the parsing of query strings more adaptable, so that we can override the
ParseFilterQuery
method to support queries likefilter[attribute][lt]=value
instead?The text was updated successfully, but these errors were encountered: