b4e97fa21f
* Add Range.Lower and Range.Upper to query config to persist custom ranges * Update CHANGELOG to mention adding query build duration support * Remove automatic application of global timeRange If a user supplies a timeRange. Add that to the queryConfig and use that to generate the SELECT statement. If a user omits a time range, do not automatically include one...yet * Update swagger.json to mention queryConfig's range * Add test to influxql AST parsing of durations with no WHERE clause * Implement first iteration of templated dashboard time range * Range is nested within query.queryConfig * DE will not use :dashboardTime: * Clarify intention with a comment * If there are no templates present, don't open the drawer * Make TemplateControlBar its own component * Rename dashTime to dashboardTime * Cleanup TemplateControlBar * Update CHANGELOG * Update TemplateControlBar min height * Polish template control bar Inspired by @lukevmorris’ screenshot with the manage button on the right * Reconstitute presentation mode styles |
||
|---|---|---|
| .. | ||
| .storybook | ||
| assets/images | ||
| spec | ||
| src | ||
| stories | ||
| webpack | ||
| .babelrc | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .npmrc | ||
| README.md | ||
| karma.conf.js | ||
| package.json | ||
| storybook.js | ||
| yarn.lock | ||
README.md
Packages
We are using yarn 0.19.1.
Adding new packages
To add a new package, run
yarn add packageName
Adding devDependency
yarn add --dev packageName
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