This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
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.
Refactor AnomalyHistory Chart to improve performance for HC detector #350
Refactor AnomalyHistory Chart to improve performance for HC detector #350
Changes from 3 commits
f7dcc40
98e3fed
2ea4946
15d18e4
f8d83ad
314e25a
0dd71b5
f9b7217
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Can we add another prop to determine if we are using actual vs. sample results, rather than reusing the
showAlerts
one? One reason for this is that those may not always coincide with each other. For example, with historical detector results,props.showAlerts
isfalse
since alerts don't apply, but it is also not sample results.I'm reusing the
AnomalyHistory
component in the historical detector results page, and have actually added a prop to handle this (as well as for all of the necessary children components) here. I'm wondering if you can maybe do something similar here. Will help with possible merge conflicts down the road as well. Let me know what 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.
Yeah, I was thinking about the same thing. Sure. I can add same prop as you did,
isNotSample
. For my PR, I will haveisNotSample
in Heatmap Chart Props, but keep usingprops.showAlert
for input of heatmap chart so that we can have as less conflict as possible. I will change to useisNotSample
once your change is merged.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.
Got it, sounds good.