Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[URL to the resource here.]
https://github.com/sophiabits/graphql-sunset
[Explain what this resource is all about and why it should be included here.]
Sunset
is a standard HTTP header used to communicate that a resource will become unavailable in future. This signaling is important as it gives consumers warning for them to move off the deprecated resource before removal, and because theSunset
header is interpretable programmatically consumers can build nice alerting systems around it (WeWork has done this, for instance: https://github.com/wework/faraday-sunset)This library offers a simple and easy way to add support for this header to GraphQL servers. Schema resources can be annotated with an
@sunset
directive, and the server will automatically send back aSunset
response header to any consumer that requests those marked resources.