* graph: sort series in the same order as legend
closes#9538
* style: use function arrows
* graph: remove sort by legend option
sort series based on legend by default is sort order
is set and stack is enabled
* graph: remove useless sort
* graph: make code simpler
* webpack poc, this is not going to work for plugins, dam
* tech: webpack and systemjs for plugins starting to work
* tech: webpack and systemjs combo starting to work
* tech: webpack + karma tests progress
* tech: webpack + karma progress
* tech: working on tests
* tech: webpack
* tech: webpack + karma, all tests pass
* tech: webpack + karma, all tests pass
* tech: webpack all tests pass
* webpack: getting closer
* tech: webpack progress
* webpack: further build refinements
* webpack: ng annotate fixes
* webpack: optimized build fix
* tech: minor fix for elasticsearch
* tech: webpack + ace editor
* tech: restored lodash move mixin compatability
* tech: added enzyme react test and upgraded to react v16
* tech: package version fix
* tech: added testdata to built in bundle
* webpack: sass progress
* tech: prod & dev build is working for the sass
* tech: clean up unused grunt stuff and moved to scripts folder
* tech: added vendor and manifest chunks, updated readme and docs
* tech: webpack finishing touches
Fixes#8872. Use the automatic calculation by Flot to get the
number of decimal places for ticks on the y-axis rather than
the number of decimal places for the min value.
If there are too many ticks generated for the y-axis (which can occur
for log scale 2, with a small y-min and a large max), then the ticks
will be regenerated using larger jumps between the ticks.
This also handles the case when y-min is set to 0. Previously, y-min of
0 was ignored as zero is not a valid value for log scale. Now the tick
generator approximates zero by setting min to 0.1.
Ref #8244
Ref #8516
fixes#8446. Data with all values equal to zero, creates a max with the
value of Infinite. The for loop for creating ticks then gets stuck in an
infinite loop. This fix resets min and max and creates some fake ticks
for the y-axis if the min and max are not finite numbers.
* graph: initial histogram support #600
* graph histogram mode: add Bars number option
* graph histogram mode: fix X axis ticks calculation
* graph histogram mode: change bar style (align and width)
* refactor(graph): move histogram functions into separate module
* graph histogram mode: rename series to "count"
* graph histogram mode: fix errors if no data
* refactor(graph and heatmap): move shared code into app/core
* graph: add tests for histogram mode
This is an old PR so had some problems after merging in master.
- Fix for min and max that were not getting passed into the
applyLogScale function
- Fix for when min/max were undefined rather than null
- Fix for decimal ticks, as this PR populates the ticks itself then
it also needs to calculate the number of decimal places too. Flot
was showing the wrong number of decimal places sometimes otherwise
on the y-axis.
* fix(flexible_y-min/max): fixed negative values support and added tests for this.
* fix(flexible_y-min/max): fixed issue with Y-Min and Y-Max values stored as numbers.
Issue: panels with configured Y-Min and Y-Max don't display anything
after upgrade.
* Feature: Flexible Y-Min and Y-Max settings.
Y-Min and Y-Max is now string.
New usage for both Y-Min and Y-Max (Where X is a real number):
>X Y-Max/Y-Max is auto if data is above X else X
<X Y-Max/Y-Min is auto if data is below X else X
=X Y-Max/Y-Min is scaled to current value +/- X
~X Y-Max/Y-Min is caled to average value +/- X
Example: Y-Min: <100 Y-Max: >200
If all points are within 100 and 200: Y-Min is 100 and Y-Max is 200
If some points are above 200: Y-Min is 100 and Y-Max is auto
If some points are below 100: Y-Min is auto and Y-Max is 200
if some points are below 100 and above 200: Y-Min and Y-Max is auto
Tests for new settings added
* Use parseFloat instead of implicit conversion
* feat(flexible_y-min/max): refactor.
* feat(flexible_y-min/max): added more tests.