-
Notifications
You must be signed in to change notification settings - Fork 7
Plotting Improvements - Series color scale and color picker options #7247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
1166f96
LABKEY.vis.Scale.ValueMapDiscrete to support an D3 like ordinal scale…
cnathe 704f8b7
GenericChartHelper.generatePlotConfig() update to use chartConfig mea…
cnathe 2f51c16
vis demo update to use LABKEY.vis.Scale.ValueMapDiscrete
cnathe a5ff2fa
Merge branch 'develop' into fb_chartColorScale
cnathe 3e1ca00
Box plot points layer to be added last, after the box layer
cnathe 52a713c
remove testing code
cnathe 1ef675d
Merge branch 'develop' into fb_chartColorScale
cnathe b4219cd
Merge branch 'develop' into fb_chartColorScale
cnathe File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The no-arguments case for domain, and range, are probably incorrect, since they are not including the values from the valueMap. However, I am not sure how much this matters, I'm not sure if we rely on the domain/range getters for discrete scales at all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Though it's hard to say if they're definitely incorrect, since I suppose those are the domain and range for the "fallback" scales used by ValueMapDiscrete. One could argue they could be implemented as such:
domain =
Array.from(Object.keys()).concat(domain)range =
Array.from(Object.values).concat(range)However there would then be no way to tell what part of the domain or range are part of the "fallback" scale.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I went back and forth on these implementation for scale.domain and scale.range. It is possible that the valueMap includes keys that aren't in the actual data being plotted, so I went this route.