Skip to content
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 useStrictQuery, and use strict for both options #9015

Closed
AbdelrahmanHafez opened this issue May 16, 2020 · 2 comments
Closed

remove useStrictQuery, and use strict for both options #9015

AbdelrahmanHafez opened this issue May 16, 2020 · 2 comments
Assignees
Milestone

Comments

@AbdelrahmanHafez
Copy link
Collaborator

on strictQuery docs it mentions that

For backwards compatibility, the strict option does not apply to the filter parameter for queries.

6.0 is a good opportunity to get rid of it, and use strict option for it by default.

@jonchurch
Copy link
Contributor

I'm curious about the context around this change, is there an issue where this was discussed?

@vkarpov15
Copy link
Collaborator

@jonchurch TBH we should have had more discussion about this. We thought it would be good to remove an extra option, but missed that removing the option had some undesirable consequences.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants