Added optional valueField config setting when wanting to use another … #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…valuefield than graph.valueField
|
Please let me know, if I have to make any changes to get merged @martynasma :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…valuefield than graph.valueField.
When using "openField" together with "valueField" bestFitLine doesn't take the total range in to account. Only the valueField.
By adding graph.bestFitLine.valueField config, it is possible to change the column from the dataprovider that the trend line is calculated from and thereby using a calculated total value instead of the maximum value.
I have not minified the file.