-
Notifications
You must be signed in to change notification settings - Fork 121
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
feat(series): stack series in percentage mode #250
Changes from 7 commits
d7ddda3
230c7c6
aa6f435
e73de20
ef987e6
7dd23ff
501289c
32bd14a
3093ec9
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -96,6 +96,10 @@ export interface SeriesAccessors { | |
splitSeriesAccessors?: Accessor[]; | ||
/** An array of fields thats indicates the stack membership */ | ||
stackAccessors?: Accessor[]; | ||
/** | ||
* Stack each series in percentage for each point. | ||
*/ | ||
stackAsPercentage?: boolean; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It is possible to define a series with empty/undefined I don't think this needs to be addressed in this PR because we also have a few other "impossible states" that can be configured currently, but wanted to start the discussion in case that is something we want to explore. This is a talk about how to achieve such a semantics in Elm, but certainly not unique to Elm and something that we could do using Typescript/React. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sure, that should be addressed here: #85 |
||
/** An optional array of field name thats indicates the stack membership */ | ||
colorAccessors?: Accessor[]; | ||
} | ||
|
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.
Should we use the
Domain
type here?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.
Yes and no. On the Y Axis we, currently can handle only numeric values, so the domain here is
number[]
, or better: it should be[number, number]
. What do you think?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.
ahhh yes, of course. Yes I agree
[number, number]
; maybe in the future we can consider how to tighten theDomain
type so that we can between distinguish between types of domains so it is clearer.