feat: filter query preset constraints #12485
Merged
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
You can now specify exactly who can change the constraints within a query preset.
For example, you want to ensure that only "admins" are allowed to set a preset to "everyone".
To do this, you can use the new
queryPresets.filterConstraintsproperty. When a user lacks the permission to change a constraint, the option will either be hidden from them or disabled if it is already set.The
filterConstraintsfunctions takes the same arguments asreduceOptionsproperty on select fields introduced in #12487.