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.
domainMin and domainMax not always respected
See original GitHub issuedomainMin and domainMax are not always respected, despite domain behaving correctly.
In Example 1, we can see neither being respected. Modifying them (such as in Example 3) we can see that they are sometimes respected. It’s not clear under what circumstances they are or are not respected.
However, adding in the domain property with the very same values immediately addresses the issue (see Example 2) I would not expect domainMin and domainMax to behave any differently from the use of domain. While domain is a reasonable hack around the problem, there are times where we need to specify only one or the other side of the range and domain requires both a min AND max.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:6 (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
sure!
I think the issue here is nicing. If you set
nice: false, it looks like your example is correct. Open the Chart in the Vega EditorWe could set nice to false if domainMin and/or domainMax are set.