-
Notifications
You must be signed in to change notification settings - Fork 176
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
Bugfix/1.9.0 fixes #220
Bugfix/1.9.0 fixes #220
Conversation
@@ -753,7 +753,7 @@ export class LineChart extends BaseVisualization<LineChartState> { | |||
} | |||
|
|||
getDatasetXRange(dataset: Dataset, continuousDimension: Dimension): PlywoodRange { | |||
if (!dataset) return null; | |||
if (!dataset || dataset.data.length === 0) return null; |
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.
could we use dataset.count() instead of chain of properties?
@@ -62,6 +62,7 @@ const numberSplitConversion: SplitDefinitionConversion<NumberSplitDefinition> = | |||
toSplitCombine(split: NumberSplitDefinition): Split { | |||
const { dimension, limit, sort, granularity } = split; | |||
return new Split({ | |||
type: SplitType.number, |
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.
Is it feasible to enhance split definition tests to cover this change?
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.
It's covered via viewDefinition converter, which are failing right now. I'm on it.
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.
OTOH, I'm thinking about overriding Split constructor, so you need provide all fields - no default values.
No description provided.