You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is probably one of those features which needs adopting at both the Graphiti level and in Pioneer but it would be awesome if we could create our own directives.
The most obvious and helpful one would be some form of Auth directive documented here. This could feed into Vapor's authentication solution to allow us to only return certain types or fields if the user is authenticated to view them.
This is kind of possible loosely with the validation rules released in #72, however that has a couple flaws:
The rules are not made fully transparent to the end user which could cause them to make requests they're not eligible unintentionally and cause confusion
An error thrown in a validation rule will prevent any of the request from being made. It would be nice if, for example, the user requested 5 fields and only one of them was protected to still return the other 4.
The text was updated successfully, but these errors were encountered:
This is probably one of those features which needs adopting at both the Graphiti level and in Pioneer but it would be awesome if we could create our own directives.
The most obvious and helpful one would be some form of Auth directive documented here. This could feed into Vapor's authentication solution to allow us to only return certain types or fields if the user is authenticated to view them.
This is kind of possible loosely with the validation rules released in #72, however that has a couple flaws:
The text was updated successfully, but these errors were encountered: