Make Env File Easier to Read by Grouping Variables Together #44
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…configuration file together
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Before, we used to sort all variables in alphabetical order. This made variables from the same config file appear in different places, which could be confusing. To fix this, we've changed how we sort variables.
Now, we sort variables by the config file they belong to first. Then, we sort them alphabetically within each file group. This change makes our .env file easier to read because related variables stay together.
This update makes it simpler to work with our .env file, especially when adding, changing, or looking for variables. We hope this will make things easier for everyone and reduce mistakes. If anyone has ideas on how to make things even better, please let us know!