-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[Fix] Create and Delete navigation item mutations #5715
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
Conversation
a745646 to
d513593
Compare
Signed-off-by: trojanh <[email protected]>
Signed-off-by: trojanh <[email protected]>
|
I think
|
Signed-off-by: trojanh <[email protected]>
mikemurray
left a comment
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.
👍 Failing tests look unrelated/happening to a bunch of other open PR's
|
Thanks, @mikemurray for reviewing my PR, let me know if I could do anything to fix the failing tests. |
|
@trojanh Thank you. Can you merge latest |
|
@trojanh Ping. See my comment above. |
|
Sorry for the delay @aldeed it was Diwali so couldn't revert back, appreciate the reminder though. I have pulled the latest develop branch so it should fix the issue. |
Signed-off-by: Eric Dobbertin <[email protected]>
Resolves none
Impact: breaking
Type: bugfix
Issue
Creating Navigation Item from Reaction Admin UI breaks for anyone other than the owner.
Solution
Supplying
shopIdtouserHasPermissionfixes the above issue and the non-owner user is able to add the NavigationItem.Breaking changes
Steps to reproduce:
corepermission but not as anOwnerNavigationItemdoesn't appear in the list.This works fine for the Owner. The problem was the method was called with a missing parameter for
userHasPermissionwhich also expectsroleGroupparameter which isshopIdfor us.Testing
corepermission but not as anOwnerNavigationItemappears on the list.