-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
GraphQL: ACL #5957
GraphQL: ACL #5957
Conversation
Moumouls
commented
Aug 22, 2019
•
edited
Loading
edited
It looks good! |
@davimacedo i think here to be more clear and avoid security risk for developers, it's better to require This adds a few more fields to the mutations but it will be much easier to create and maintain them Note: |
I am not sure I understood. Could you update the schema with the change you want? |
I think i can finish it tomorrow then you will see in tests how it works. 👍 |
I tried to make the management of ACLs easy as possible. Tell me what you think about it @davimacedo ? |
Codecov Report
@@ Coverage Diff @@
## master #5957 +/- ##
==========================================
+ Coverage 93.74% 93.75% +<.01%
==========================================
Files 156 156
Lines 10939 10985 +46
==========================================
+ Hits 10255 10299 +44
- Misses 684 686 +2
Continue to review full report at Codecov.
|
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #5957 +/- ##
==========================================
+ Coverage 93.74% 93.75% +<.01%
==========================================
Files 156 156
Lines 10939 10985 +46
==========================================
+ Hits 10255 10299 +44
- Misses 684 686 +2
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #5957 +/- ##
===========================================
+ Coverage 83.28% 93.76% +10.48%
===========================================
Files 165 165
Lines 11161 11199 +38
===========================================
+ Hits 9295 10501 +1206
+ Misses 1866 698 -1168
Continue to review full report at Codecov.
|
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.
thanks for tackling this one @Moumouls . It is a great job! I've just left some questions to make sure I have understood how the defaults work.
@Moumouls I've just done some tests here. It is possible
|
I was working on another issue today and I also noticed (I haven't never noticed it before) that, when using the Parse Dashboard, if you set |
I think it could be confusing for developers. May be it could be an esay improvement if we get some feedback on this special behavior |
Yes. I agree with you. What about the other comments I left? |
# Conflicts: # src/GraphQL/loaders/parseClassTypes.js
So, to avoid misunderstanding and confusion about ACL behavior through the GraphQL API. I set the |
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.
Just one more comment. We are almost there :)
if (rule !== '*' && rule.indexOf('role:') !== 0) { | ||
users.push({ | ||
userId: rule, | ||
read: p[rule].read || p[rule].write ? true : false, |
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.
Why || p[rule].write
?
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.
good catch ! Just a miss from my part
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!
* Spec Fix Spec * Add ACL Type + Input * Improvements * Fix