Skip to content

Commit f2197f9

Browse files
committed
update readme in root folder and modules/components
1 parent a68e365 commit f2197f9

File tree

3 files changed

+32
-8
lines changed

3 files changed

+32
-8
lines changed

README.md

+1-3
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,4 @@
33
### Getting Started
44

55
Ensure you are using node version 14.19.0 and npm version 6.14.6. To manage different versions of node, we recommend using a [node version manager](https://github.com/tj/n)
6-
7-
Navigate to `modules/components` and follow the README there for setup and development guides.
8-
6+
Move to the branch `portal-ui` and install the dependencies. Once completed, navigate to `modules/components` and follow the README there for setup and development guides.

modules/components/README.md

+31-5
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,35 @@
1-
# Data Portal Components
1+
## Development Setup
22

3-
## Roadmap
3+
Make sure you are checked out in the `portal-ui` branch.
44

5-
#### Aggregations
5+
Ensure you are using node version `14.19.0` and npm version `6.14.6`. To manage different versions of node, we recommend using a [node version manager.](https://github.com/tj/n)
6+
Please note Portal uses version node version `16.13.2` and npm version `9.1.2`
67

7-
#### SQON aka "Current Filters"
8+
Inside of `modules/components` you will need to create a file called `.npmrc`. This file is required to publish updates and properly installing the dependencies for this project.The `components` module is to be published in order for Portal to consume the latest changes. In this file you will want to add the following:
89

9-
#### ResultsTable
10+
```
11+
@pilotdataplatform:registry=https://npm.pkg.github.com
12+
//npm.pkg.github.com/:_authToken=<PERSONAL_ACCESS_TOKEN>
13+
```
14+
15+
If you do not have a personal access token you will need to create one via github. Hover over your profile, go to settings > developer settings > personal access tokens > Tokens (classic). Set the expiry date to a year from the date of creation and ensure you have only read / write package permissions.
16+
17+
![Github personal access token creation](docs/images/github-personal-access-token.png)
18+
19+
Now we're ready to install the packages. Ensure you are in `modules/components` and input `npm install` in the terminal. If you encounter any issues with installing your packages, it is likely your token has expired. The error message in the terminal should display a file path to inspect your logs for more detailed troubleshooting.
20+
21+
Upon completing the installation, input `npm run start` to start up the local server. Once it loads you will be required to login with your dev environment credentials, or if you have an instance of the dev environment opened you will be logged in automatically.
22+
23+
`modules/components/src/App.js` is the entry point of the local development server.
24+
25+
## Publishing
26+
27+
### Arranger
28+
29+
Once you have finished with your changes, the components module will have to be published. In order to do so, increment the version number in `module/components/package.json`. Now, in the terminal input `npm publish`. Using your credentials in the `.npmrc` file, this script will build the project and publish it to github's package repo.
30+
31+
### Portal
32+
33+
To get the latest updates, ensure you run `npm install` for the latest version of the arranger package. For example, to install arranger version 1.5.11 you will need to input `npm install @pilotdataplatform/arranger-components/@1.5.11.
34+
35+
Upon updating the version, ensure it runs correctly locally and submit the changes through a PR.
Loading

0 commit comments

Comments
 (0)