Unable to create chart with json and dot in key
See original GitHub issueI have tried to create a donut
chart for Chrome version. Which contain a dot as key. This will cause errors. I have tried to create the chart on http://c3js.org (c3.min-4c5bef8f.js) with a chrome (50.0). But it was not possible.
var chart = c3.generate({
data: {
json: [
{'38.0': 10, '46.0': 10, '47.0': 10, '49.0': 20, '50.0': 30, 'unbekannt': 4}
],
keys: {
value: ['38.0', '46.0', '47.0', '49.0', '50.0', 'unbekannt']
},
type : 'donut'
},
donut: {
title: "Chrome Versions"
}
});
Issue Analytics
- State:
- Created 7 years ago
- Reactions:5
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Fetch and Display Advanced JSON Data in Chart JS - YouTube
To do this we need to create a JSON file before we can use it with Chart.js. We will be fetching data and...
Read more >Returning fetched JSON correctly but can't get it into Chart.JS
You have to wait for the fetch-request and its data to create your chart or you have to update it when your data...
Read more >Data From JSON | Working with Data - AnyChart Documentation
AnyChart js charting library supports several ways of setting data. This article quickly demonstrates main aspects of using JSON format in AnyChart L....
Read more >helm v3.0 mapping values are not allowed in this context #6251
I get the same error message with our SonarQube chart for OpenShift. The same install works with Helm v2. > helm3 repo add...
Read more >JSON editing in Visual Studio Code
Editing JSON with Visual Studio Code. JSON is a data format that is common in configuration files like package.json or project.json .
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It seems that this issue is still open in the current version, isn’t it?
We have a problem similar to the described behavior.
I have this problem too, how we can solve this ?