-
Notifications
You must be signed in to change notification settings - Fork 130
Expose user-defined directives in API schema #387
Comments
Comment by kbrandwijk Generic feature request for https://github.com/graphcool/framework/issues/1032 too. |
Comment by develomark I'd like to add my +1 for this feature request. With 1.0 coming up to release it puts a lot more power in the hands of the developer - I see this as a critical feature for its release. These directives will help to facilitate configuration of business logic - permissions, conditionals, caching, metadata etc. The ideal situation would be: on Any directives or descriptions should also pass to Input Definitions also.
|
Comment by develomark @schickling Is there a possibility this could be added to the 1.0 feature list? |
Comment by kbrandwijk Especially because it already preserves custom directives on fields, this is now in an inconsistent state that should be addressed. It's also blocking for quite a number of use cases. |
Issue by schickling
Thursday Nov 09, 2017 at 11:16 GMT
Originally opened as https://github.com/graphcool/prisma/issues/1228
Graphcool currently supports a limited number of system directives which are used in the data model to construct the API. These system directives are not exposed through the GraphQL API. (Other directives are currently not accepted and will result in a deploy error.)
However, there are many other use cases (like in this forum post) for directives where you'd want to expose them directly in the GraphQL API.
The text was updated successfully, but these errors were encountered: