Respect example username setting #648
Closed
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 your pull request is reviewed and merged, please ensure that:
there are no linting errors --
npm run lint
(There are linting errors, but not from any of the files I have touched. Do you still want me to fix these?).your code is in a uniquely-named feature branch and has been rebased on top of the latest master. If you're asked to make more changes, make sure you rebase onto master then too!
your pull request is descriptively named and links to an issue number, i.e.
Fixes #646
This pull request addresses Issue #646. It improves the wording of the readme to clarify that the example user will be created with whatever username is provided in the
.env
file and also uses this value in the code. Previously, several locations in the code used a hard-coded value of "p5" for the example user.I am an absolute novice with node and react, so please check that what I've done is sensible!