Expose taxonomy and post type capabilities in context==edit#2216
Expose taxonomy and post type capabilities in context==edit#2216rachelbaker merged 1 commit intodevelopfrom
context==edit#2216Conversation
|
@WP-API/amigos #reviewmerge |
|
This should ship with a giant warning that just because a user has the capability described, does not mean they will be able to perform the action. |
I think I understand what you're saying, but I'm not sure where it would fit in. How would you present such a warning? |
Expose taxonomy and post type capabilities in `context==edit`
|
I think it makes sense to add a warning to the documentation, with an example of a case or two that can be problematic. This change was prompted by some discussion in Slack: https://wordpress.slack.com/archives/core-restapi/p1454367860000776 To summarize - we do a lot of capabilities checking in Calypso, mainly so that we can go ahead and disable UI elements and/or show messages if we are certain that the user will not be able to perform an action. This isn't perfect - as you said, we still need to be sure we handle errors correctly - but it's still very useful. |
There was a problem hiding this comment.
Missing full-stop on the sentence here.
5 participants
No description provided.