* Use client generated Label in dashboard actions * Fetch labels when dashboards index loads * Add styles for "colorless" labels * Implement inline label editing from dashboard cards * Fine tune label deletion * Create createLabelAJAX function Co-Authored-By: Delmer <ofthedelmer@users.noreply.github.com> * Make inline label creation work in dashboards index Co-Authored-By: Delmer <ofthedelmer@users.noreply.github.com> * WIP use ILabel as the defacto label type * Ensure a label can be updated without having to change the name * Ensure all fields in a Label can be changed in the overlay * WIP write e2e tests for inline labelling Co-Authored-By: Andrew Watkins <121watts@users.noreply.github.com> * wip: dashboard brittle * wip dashboards * Position inline labels popover such that it doesn't collide with the navbar * chore: run all dashboard tests 25 times * Ensure that there is a dashboard with a name that matches the search test query * Appease the lint gods with mortal sacrifice * Remove unit test in favor of e2e test Everything the unit test is testing is also tested by the e2e test Co-Authored-By: Delmer <ofthedelmer@users.noreply.github.com> * Remove for loop and fix search name assertion Co-Authored-By: Delmer <ofthedelmer@users.noreply.github.com> Co-Authored-By: Andrew Watkins <121watts@users.noreply.github.com> * Fix affected task test Co-Authored-By: Delmer <ofthedelmer@users.noreply.github.com> Co-Authored-By: Andrew Watkins <121watts@users.noreply.github.com> * Fix incorrectly named reference in e2e test Co-Authored-By: Delmer <ofthedelmer@users.noreply.github.com> Co-Authored-By: Andrew Watkins <121watts@users.noreply.github.com> * Undo go file change * Add guard back in * Undo changes to go file |
||
---|---|---|
.. | ||
assets/images | ||
cypress | ||
mocks | ||
src | ||
.browserslistrc | ||
.eslintrc.json | ||
.npmrc | ||
.prettierrc.json | ||
Makefile | ||
README.md | ||
cypress.json | ||
index.d.ts | ||
jestSetup.ts | ||
package-lock.json | ||
package.json | ||
testSetup.ts | ||
tsconfig.json |
README.md
Packages
Adding new packages
To add a new package, run
npm i packageName
Adding devDependency
npm i packageName -D
Updating a package
First, run
npm 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
:
npm upgrade packageName
Testing
Tests can be run via command line with npm test
, from within the /ui
directory. For more detailed reporting, use yarn test -- --reporters=verbose
.