refactor!(crud): apply parameter naming conventions #3291
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.
Let's try to stick to agreed naming conventions as much as possible: for a feature
X
, especially if boolean, let's avoid prefixes and suffixes likeno
orVisible
. So, for example,noHeaderFilters
becomesheaderFilters
, anddeleteButtonVisible
becomesdeleteButton
.The recently introduced
newButton
toggler already respects this convention.Closes #3258.