feat: User setting "default capability app view" #102
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.
preliminary work for EDUPL-15
@MasterMarcoHD @mcquenji this new user setting lets the app save what capability to act as per default. There are currently 4 valid states:
The numers are just the usual capability flags - see
CAPABILITY_FLAG.phpandCAPABILITY_FLAG_ORNONE.php.As usual, this new user setting is optional when calling update_user, meaning the frontend can implement this whenever you feel like it.
Note that we don't perform any checks on whether a user actually has the preferred capability - I suggest simply not showing invalid configurations in the app (you would have to do that anyway) - and that this setting has no effect on other plugin operations. Also note that this currently only has use for the slot view, but I made it more generalized with potential future features in mind.
If there are any changes I should make, please press "request changes" and we can discuss in a meeting. If not, please approve. Thanks!