-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more permission checks #1825
Conversation
Size Change: -61 B (0%) Total Size: 872 kB
ℹ️ View Unchanged
|
Codecov Report
@@ Coverage Diff @@
## master #1825 +/- ##
============================================
+ Coverage 63.79% 63.96% +0.17%
Complexity 235 235
============================================
Files 587 588 +1
Lines 9572 9602 +30
============================================
+ Hits 6106 6142 +36
+ Misses 3466 3460 -6
|
return ( | ||
<Primary onClick={handlePublish} isDisabled={isSaving || isUploading}> | ||
<Primary |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose it's a UX question but should this be displayed at all without the correct permissions?
If we show anything then maybe we would need to bring in the pending
status and use the "Submit for Review" option as in WordPress. This would need to be confirmed by UX though.
I'm just wondering how to make sure the "Publish" button doesn't feel broken if it's disabled due to a lack of permissions.
Maybe keep as is but follow up with UX? WDYT?
@@ -69,17 +67,20 @@ function StatusPanel() { | |||
name: __('Draft', 'web-stories'), | |||
helper: __('Visible to just me', 'web-stories'), | |||
}, | |||
{ | |||
]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If Draft
is the only option available in radios then better to not show the radio at all. Might be a bit odd seeing a radio selection with just one option. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't really have UX for this now. The UX might not be the best, but good enough for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good to me to keep as-is for now but please follow up with @samitron7 so that she would be aware of this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but please follow up with Sam so that she would be aware of permissions influencing what's displayed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A bit odd that statuses
hasn't really been used in the past.
Overall looks OK, but please get final sign-off from workspace pod & make sure to track this with UX.
Summary
When testing the editor a subscriber, I that neither the publish story button wasn't disabled. Also none of the current status were showing.
In this PR,
Relevant Technical Choices
To-do
User-facing changes
Current
After this PR
Testing Instructions
See #1390