fixes for duane/ts-options #1012
Closed
Conversation
This file contains hidden or 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
|
Ah, we should add string & {} to allow arbitrary strings (or enumerate the colors) to ValueAccessor |
|
I've added some of the changes you made, as well as unit tests, to the fil/ts-options branch (#1008). |
|
obsolete |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
@duaneatat Some changes to your PR so that it validates, but when I add these files into #1005, everything breaks.
The reason, I suspect, is that some value accessors are legitimately not DatumKeys, even if the datum is a {key:value} object. For example, in
Plot.dotX([{value: 10}], {fill: "red", x: "value"})the fill accessor is legal.