Split isFulfilledData
into isFulfilledBarData
and isFulfilledLineData
to allow WhitespaceData
with extra properties
#1579
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.
Type of PR: enhancement
PR checklist:
value
and notopen
#1526Overview of change:
isFulfilledData
was used to validate bothOhlcData
andSingleValueData
, but based on different keys. This will cause a false assertion to be thrown when validWhitespaceData
is passed but also includes extra keys which cause it to be considered to be "fulfilled" but for the other series type. Also, this validation only occurs in development.This PR introduces
isFulfilledBarData
forOhlcData
, andisFulfilledLineData
forSingleValueData
. Specifically only considering the propertiesopen
vsvalue
instead of either being present.Is there anything you'd like reviewers to focus on?
In the function
_convertMouseParams
, instead of callingisFulfilled*Data
directly, it could reuse the method from before.getChecker(seriesType)(data)
. AlsoisFulfilledData
could be removed and merged intocheckBarItem
/checkLineItem
and return a boolean so_convertMouseParams
can be asserted the same. This seemed beyond the initial intention, let me know.