Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Provide clear error message for incompatible color schemes.
See original GitHub issueI was directed here after logging https://github.com/altair-viz/altair/issues/1603
When I accidentally used a discrete colour map for continuous data, I got the error
Javascript Error: e is undefined
i.e.
color=alt.Color('Loss', scale=alt.Scale(scheme=‘dark2’))
I should have used
color=alt.Color('Loss', scale=alt.Scale(scheme=‘viridis’))
Sorry, I’m not sure how to express this as vega-lite syntax, but it seems to me there’s potentially a bug as the error message seems to indicate that there’s an exception handler missing an e argument somewhere?
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
In addition to better error warning, this issue also revealed an issue in color scheme handling. Array-valued schemes can be interpolated to be used within interpolating scale types. This was already supported for array literals as the scale
range, but not for named schemes. PR #1950 fixes this bug and also adds a new, friendlier warning for incompatible schemes.Alright, I thought the same applies to the
colorargument. Will open a separate issue then.