* refactor(ui): create shared component for settings pages * refactor(ui): use clockface tabs in settings nav * refactor(ui): ensure all settings pages use SettingsTabbedPage component * refactor(ui): replace TabsContentHeader with SettingsTabbedPageHeader * refactor(ui): remove unused logic from when tasks page was rendered in 2 places * refactor(ui): add testID to searchWidget * refactor(ui): standardize use of SearchWidget across settings pages * refactor(ui): delete locally defined Tabs components * refactor(ui): appease the linter gods |
||
---|---|---|
.. | ||
__mocks__/@influxdata | ||
assets | ||
cypress | ||
mocks | ||
scripts | ||
src | ||
.browserslistrc | ||
.eslintignore | ||
.eslintrc.js | ||
.npmrc | ||
.prettierrc.json | ||
Makefile | ||
README.md | ||
cypress.json | ||
index.d.ts | ||
jestSetup.ts | ||
package.json | ||
testSetup.ts | ||
tsconfig.json | ||
webpack.common.ts | ||
webpack.dev.ts | ||
webpack.prod.ts | ||
webpack.tsconfig.json | ||
webpack.vendor.ts | ||
yarn.lock |
README.md
Packages
Adding new packages
To add a new package, run
yarn add packageName
Adding devDependency
yarn add packageName --dev
Updating a package
First, run
yarn outdated
... to determine which packages may need upgrading.
We really should not upgrade all packages at once, but, one at a time and make darn sure to test.
To upgrade a single package named packageName
:
yarn upgrade packageName
Testing
Tests can be run via command line with yarn test
, from within the /ui
directory. For more detailed reporting, use yarn test -- --reporters=verbose
.
Starting Dev Server
The assets are built by running yarn start
from withing the /ui
directory. The dev server with hot reloading runs at localhost:8080
.