Field type permissions
See original GitHub issueHi! I have tested permissions applied to type which is returned from query and it seems not to work when resolvers for type were not explicitly defined: for e.g. this works when I do query me:
const resolvers = {
Query: {
me: (_, args, ctx) => ctx.user;
},
User: {
name(parent, args, ctx) { return parent.name; }
}
}
const permissions = shield({
User: {
name: allow
}
})
and this doesn’t, although it has allow rule:
const resolvers = {
Query: {
me: (_, args, ctx) => ctx.user;
}
}
const permissions = shield({
User: {
name: allow
}
})
Always getting Not Authorised! error.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
Field Permissions - Salesforce Help
Field permissions specify the access level for each field in an object. In permission sets and the enhanced profile user interface, the setting...
Read more >Type Field Permissions - SmartWiki
The Type Field Permissions control the visibility of the field or button for ... Allow View Field – Defines on which templates/types the...
Read more >Field Permissions | Drupal.org
The Field Permissions module allows site administrators to set field-level permissions to edit, view and create fields on any entity.
Read more >Field permissions - Documentation for Action Request System ...
Field permissions determine the types of access that groups or roles have for individual fields in a form: ... If neither permission is...
Read more >Configuring custom field permissions
In the main navigation menu go to Administer > Custom Fields. · Select a custom field. · Under Security Options, click Add Permission....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Try upgrading
graphql-yoga
to the latest version.The issue about type resolvers has been resolved in one of the latest versions of
graphql-middleware
which should have, as well, been updated in Yoga.Tell me if that worked out for you! 🙂
No problem, I am glad it worked 😄