Closed cryzed closed 8 years ago
Leather takes the opinionated stance that you intend for the type to be the one you provide. If you want to do bar or column labels, those have to be text, so you have to supply text. The bug you're hitting is because by supplying numbers agate assumes you intend to position the bars as intervals across a linear domain, which I haven't implemented yet (though I will).
Going to close this ticket out. I do think it's confusing now, but once the LinearScale interval method is implemented the behavior will be consistent with other scale/data types.
I see, that makes sense.
Currently using non-string key values in the data set is impossible. When changing the columns example to only include non-string values the following exception is thrown:
The object's string representation should be used for the text display in the chart. Comparison between used key objects (for sorting etc.) can obviously still be done before coercing them to strings.