@aws-amplify/graphql-directives
Advanced tools
Directive definitions for Amplify GraphQL transformers.
Source of truth for the GraphQL directive definition used by the Amplify GraphQL API.
:warning: Intended for internal Amplify use only.
This package defines the GraphQL directives in GraphQL syntax. Each directive is imported into the corresponding GraphQL transformer. This package is responsible for the name, definition, and argument defaults for a directive. The GraphQL transformers utilize the GraphQL directives to define the behavior of the transform.
This package also contains the AppSync GraphQL directives. These directives are defined internally by AppSync. The definitions here are copied from the internal definition.
This package is intended to be the only source of truth for the GraphQL directive definitions used by the Amplify GraphQL API. This package should be imported in place of reproducing the definitions in other packages.
FAQs
Directive definitions for Amplify GraphQL transformers.
The npm package @aws-amplify/graphql-directives receives a total of 45,951 weekly downloads. As such, @aws-amplify/graphql-directives popularity was classified as popular.
We found that @aws-amplify/graphql-directives demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 9 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
In an open letter, JavaScript community leaders urge Oracle to give up the JavaScript trademark, arguing that it has been effectively abandoned through nonuse.
Security News
The initial version of the Socket Python SDK is now on PyPI, enabling developers to more easily interact with the Socket REST API in Python projects.
Security News
Floating dependency ranges in npm can introduce instability and security risks into your project by allowing unverified or incompatible versions to be installed automatically, leading to unpredictable behavior and potential conflicts.
