fix: explicitly check the type of Accounts_AllowUserStatusMessageChange
#5642
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.
Proposed changes
allowUserStatusMessageChange
can betrue
,false
orundefined
We should only disable status change if it is explicitly
false
.Issue(s)
How to test or reproduce
Enable or disable the setting and see if the status change menu is visible or not.
Also check on a server that has not changed this setting (which must have the value of
undefined
), to see if the option exists or not.Screenshots
Types of changes
Checklist
Further comments
Jira: SUP-536