fix: issue#30, semanticType runtime error #31
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issues: #30 .
It seems
targetVisfails to handle the case when the field does not exist, which is possible because the recommended visual specification could provide encodings without color channel.The same case had been considered in
featureVis, but forgotten intargetVis.However, normally, data views targetVis get should have at least one dimension(feature). And the auto specification has a high possibility of encoding the feature into color(perception error). (it passes tests with different dataset when developing(kaggle/titanic, kaggle/kelper, etc))
I'm curious about what channel is used for the dimension if it is not color and why(depends on the dataset).
or the dataset might contain no dimension.