Standardise the use of Hidden
and HiddenChanged
#8952
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.
MudBlazor currently uses the
IsHidden
andIsHiddenChanged
properties. This PR aims to standardise the use ofHidden
andHiddenChanged
to align with other boolean properties in the library.Description
If this PR is approved, the v7 migration guide must also be updated, as this makes a breaking change:
MudHidden: replace
IsHidden
withHidden
MudHidden: replace
IsHiddenChanged
withHiddenChanged
Linked issues:
Negative property names should be discouraged #6131
v7.0.0 Migration Guide #8447
Standardise the use of
IsEnabled
andEnabled
#8764Standardise the use of
ItemDisabled
#8887Standardise the use of
Checked
,CheckedChanged
andCheckable
#8825Standardise the use of
Visible
#8832Standardise the use of
Selected
andSelectedChanged
#8886Standardise the use of
Expanded
,Expandable
,IsExpanded
andIsExpandable
#8718Standardise the use of
Active
#8888Standardise the use of
Open
andOpenChanged
#8891Standardise the use of
Editable
#8892Standardise the use of
Hidden
andHiddenChanged
#8952How Has This Been Tested?
unit
Type of Changes
Checklist
dev
).