refactor: disable graphql playground in staging environment as well #10756
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.
What does it do?
Disable GraphQL playground in
staging
environment as well (other than production environment).Why is it needed?
Some projects might only have/run on :
How to test it?
In environment variable (
.env
file), setNODE_ENV
value tostaging
orproduction
to see the GraphQL playground disabled.Any suggestion is appreciated!