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

forced filters vs default filters #27

Open
guruofgentoo opened this issue Apr 18, 2017 · 0 comments
Open

forced filters vs default filters #27

guruofgentoo opened this issue Apr 18, 2017 · 0 comments

Comments

@guruofgentoo
Copy link
Member

Some filters are necessary to be present, in order to reduce the amount of data a grid is processing. Otherwise the results could take a very long time to complete. In other cases, they are simply user helpers which should be allowed to be cleared.

What we need is the concept of a "forced" filter, introduced by having is_forced=True in the filter constructor. Forced filters will need to require a default op, and in the UI would remove the possibility of disabling them.

"Default" filters would then need the grid to tell them if they should be processed with the default op. If the user has selected other filters, the default should be allowed to lapse.

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

1 participant