refactored env vars into new constants file #462
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.
Purpose
There is a common pattern repeated throughout the code when using some ENV vars. For example:
closes: Add github issue that originated this PR
Approach
This PR refactors most environment variables into a
constants.ts
file. The updated example is now:Open Questions and Pre-Merge TODOs
constants.ts
rely on checking ifprocess.env.NEXT_PUBLIC_API_URL === 'https://api.datacite.org'
to determine if they should use the prod or stage version of their URL. We may consider using theNODE_ENV
variable instead.NODE_ENV
to determine which URL to point to then we can remove most of the ENV vars.Learning
Types of changes
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Reviewer, please remember our guidelines: