Rephrasing setup comment #675
Closed
Conversation
This file contains 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
This commit has changed the wording of the comment in the setup section of the code for additional clarity and brevity.
|
@PieterDePauw is attempting to deploy a commit to the leerob-site Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi team, I had noticed a typo ('orderrides') in the setup.mjs file and seized the opportunity to overhaul the wording of that particular comment. In particular, I've aimed to adopt a clearer, more straightforward style to explain the usage of the 'IS_TEMPLATE' environment variable in the setup process.
The original explanation seemed a bit too convoluted and potentially confusing, especially for non-native English speakers. I believe this new structure is more user-friendly and will make the message more accessible to anyone delving into the code.