-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
23527 Changed a button label + updated README #778
Conversation
- added pnpm install instruction to README - update app title in README - updated browserslist (caniuse) - changed "Continue In Now" to "Begin Continuation"
@@ -1,9 +1,10 @@ | |||
# Name Request Online Frontend | |||
# Name Request UI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is what we always call it (and sometimes "Namerequest UI" as per the repo name).
We should not refer to "NRO" in the name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rarmitag Am I missing something here -- did the name actually change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not that I'm aware.
|
||
[![img](https://img.shields.io/badge/Lifecycle-Stable-97ca00)](https://github.com/bcgov/repomountie/blob/master/doc/lifecycle-badges.md) | ||
|
||
## Project setup | ||
``` | ||
npm install -g pnpm | ||
pnpm install |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had to look up how to use pnpm, so here I'm saving the next person a couple of minutes :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same thing happened to me a while ago. Good idea.
@@ -1,6 +1,6 @@ | |||
{ | |||
"name": "name-request", | |||
"version": "5.5.8", | |||
"version": "5.5.9", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the version number.
I assume "pnpm" updated the other package versions.
Note that I did run the command npx update-browserslist-db@latest
as recommended,
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The package updates below should make no difference because (theoretically) the ^
instructed npm/node to use the latest minor/patch versions of the package, which is what the changes below do explicitly.
In other words, even though we asked for "compat-data v7.21.5", we were already using v7.24.4 due to the ^
symbol.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
@rarmitag If this looks OK to you, please merge it. Thanks! |
Issue #: bcgov/entity#23527
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namerequest license (Apache 2.0).