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.
Enabling the Chart.js decimation plugin here replaces each dataset’s
dataarray with a ~2000-point LTTB sample whenever a series exceeds the 4k threshold. The rest ofChartContainerrelies onchart.data.datasetsfor features likeexportChartCSVand cross-chart hover sync, so large logs will now export only the decimated subset and most steps will no longer synchronize between charts because the searched x-values were removed during downsampling. Consider using the original data (_data/parsedData) for these operations or disabling decimation when exporting/syncing to avoid losing points.Useful? React with 👍 / 👎.