- Make sure you have
Node.jsandnpminstalled - Run script to patch your
/etc/hosts - Make sure you are using Red Hat proxy
There is a comprehensive quick start guide in the Storybook Documentation to setting up an Insights environment.
- Install dependencies with
npm install - Run development server with
npm run start:proxy:beta - Local version of the app will be available at https://stage.foo.redhat.com:1337/beta/insights/vulnerability/
Jest is used as the testing framework
npm run test- run all testsnpm run test -- testName- run tests for all components matchingtestNamenpm run lint- run linternpm run test:update- run all tests and update snapshotsnpm run test:watch- run tests in watch mode
Any push to the following branches will trigger a build in vulnerability-ui-build repository which will deploy to corresponding environment.
| Push to branch in this repo | Updated branch in build repo | Environment | Available at |
|---|---|---|---|
| master | stage-beta | stage beta | https://console.stage.redhat.com/beta |
| stage-stable | stage-stable | stage stable | https://console.stage.redhat.com |
| prod-beta | prod-beta | production beta | https://console.redhat.com/beta |
| prod-stable | prod-stable | production stable | https://console.redhat.com |
Translation keys are saved in messages.js.
Each time you add a new translation keys you need to run npm run translations, which will automatically generate JSON files for every language into locales/ folder based on the entries in the messages.js.
There are two ways to use translated strings:
- With
intl.formatMessage(messages.messageId) - With
<FormattedMessage {...messages.messageId}/>
This project uses Patternfly React.
This app imports components from Insights Front-end Components library. ESI tags are used to import Insights Chrome which takes care of the header, sidebar, and footer.
This project uses Semantic Versioning. Release process is automated by using Semantic Release.