charted-co / charted Goto Github PK

Currently, when going to a short url, it shows the spinner while it's fetching the data, but the input field remains empty. Instead, the input field should be immediately populated with the full url while it's fetching the data. This is especially helpful when it takes a while to get the data, so that you can still see what url it's using.

Sometimes, I have a rather small CSV output that I'd like to throw in charted.

Would be nice to be able to have the source being pasted in via a textarea, perhaps limiting the size to avoid issues.

This could even be disabled in the hosted version to avoid running into space issues in wherever it's hosted now. Instead, it could only be available when running locally or on users' own hardware.

I can give it a shot.

Hi,

I'd like to package charted to add it as an RPM to the openSUSE distribution. For this an official tarball would be needed. Please tag an initial version of charted and evtl. create a release on github.

Thanks,

Klaus

currently, when visiting a link with a file that takes a while to load, the loading indicator immediately appears but sometimes the form input remains blank for a few seconds before populating with the data url

After making a copy of the Google Sheet from the charted example and making it public, I've only been able to generate this wonky chart:

When accessing the Sheet's export link directly, I am able to download a CSV. However, when the request is routed through charted.co, it returns html.

Hopefully it's something I can fix on my end and add to the documentation! Any thoughts appreciated.

When charted refetches data and receives and error or empty data, it shows a blank screen. Instead it should keep the original chart displayed.

I.e. https://docs.google.com/a/medium.com

As it stands now, the options are stored in the query, and those options are sent to the server when the chart is accessed directly. If the options were moved to the hash, not only would some bandwidth be saved, but also the whole website could be cached client side (except for /get). No server-side processing is done to the options, so this seems like a safe change.

For example:
This http://www.charted.co/?%7B%7D would turn into this http://www.charted.co/#%7B%7D

I tried the example on charted.co in the latest Chrome:

http://www.charted.co/?%7B%22dataUrl%22%3A%22https%3A%2F%2Fdocs.google.com%2Fspreadsheets%2Fd%2F1PSaAXtklG4UyFm2lui5d4k_UNEO1laAMpzMWVh0FMTU%2Fexport%3Fgid%3D0%26format%3Dcsv%22%2C%22charts%22%3A%5B%7B%22title%22%3A%22An%20Example%20Chart%22%2C%22note%22%3A%22This%20is%20an%20example%20chart%20visualizing%20some%20fake%20data%22%7D%5D%7D

Instead of producing a chart, it gives a red warning page that cybercriminals may be trying to steal your credit card. Very likely a false positive (Due to hosting on docs.google.com), but something to avoid/work around for sure. Hope someone can pass this issue on to the webmaster of charted.co

I noticed that with Googlesheets you are using format=csv which is the old Sheets API and won't work with new spreadsheets (it still works with ones that were created before the old version of the sheets API was dropped). This is how I dealt with the problem in R, using some modified code from Andrei de Vries at Revolution
https://github.com/elinw/ShinyGoogleSheets/blob/nodata/scripts/readGoogleSheet.R

Basically the sheet needs to be published to the web (not just shared), and then you access it by appending /pubhtml.

I want to know how to use cheated to load local file ,thanks!

potentially use https://github.com/SheetJS/js-xlsx

Please add some more chart types in the page. D3 library have so many charts.

The error output looks like this:

Noticed embed wasn't working for me. Tried digging a bit deeper and noticed that the error is reproduced on the embed page (eg: https://www.charted.co/embed/46e0cd2)

Returns Uncaught TypeError: Cannot read property 'x' of undefined in the setScales() function when it attempts to calculate Math.floor(this.xScale(d.x), 0);

I’ve seen a couple of instances where people were trying to figure out which day of week was a specific date on a chart.

This will involve creating a .js file that dynamically creates an iframe with the appropriate height (so that the iframe does not have vertical scroll)

When charted receives a google spreadsheets link that isn't set to shareable, it tries to visualize the error message (resulting in a strange chart that makes no sense). Instead, it should provide an error notification saying that the link needs to be set to shareable. (It's worth also checking if there's a similar issue with dropbox links)

Using a dropbox link with permission set to "Anyone with the link can see it" but charted rendered some html:

E.g., when the line is flat on the bottom:

Since the 15th of February charts which had been working for about a year have suddenly ceased to display anything meaningful; behaving as if the Google sheets were not public.

I have created a new one: https://docs.google.com/spreadsheets/d/1i5INeh718Hj2AiKbiRq5eRL5qiekHR9Lzvs4NjCNmtc/edit?usp=sharing

which cannot be read correctly. Has some update messed things up?

Dimitri

Hi, great project!

I've noticed that lines often come under the x axis bar (when they should follow it) because of the interpolation done on the curves. This happens before/after big heaps on the graph. See on the screenshot below an illustration of the issue.

Changing any option should create a new history state

• when the series is longer than the available height, it should scroll
• the popover options for each series will need to be updated so that when it appears, it isn't cropped by the new bounding area of the scrollable area.

Checklist:

• Initial work
• Support getDefaultTitle on the server-side
• Embeds
• Database support
• Filesystem support
• Error when saving files
• Legacy urls (middleware?)

'bin' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] prestart: bin/build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] prestart script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Adil Raza\AppData\Roaming\npm-cache_logs\2018-11-11T22_36_02_317Z-debug.log

Complete log file:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]prestart: [email protected]
6 verbose lifecycle [email protected]prestart: unsafe-perm in lifecycle true
7 verbose lifecycle [email protected]prestart: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\Adil Raza\Desktop\Intel Hackathon\charted\node_modules.bin;C:\Users\Adil Raza\AppData\Roaming\npm;C:\Program Files\nodejs;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files\Git\cmd;C:\Python27;C:\Program Files\nodejs;C:\ProgramData\chocolatey\bin;C:\Ruby25-x64\bin;C:\Users\Adil Raza\AppData\Local\Microsoft\WindowsApps;C:\Users\Adil Raza\AppData\Roaming\npm;C:\Users\Adil Raza\AppData\Local\Programs\Microsoft VS Code\bin;C:\Program Files\heroku\bin;C:\Python27\Scripts
8 verbose lifecycle [email protected]prestart: CWD: C:\Users\Adil Raza\Desktop\Intel Hackathon\charted
9 silly lifecycle [email protected]prestart: Args: [ '/d /s /c', 'bin/build' ]
10 silly lifecycle [email protected]prestart: Returned: code: 1 signal: null
11 info lifecycle [email protected]~prestart: Failed to exec prestart script
12 verbose stack Error: [email protected] prestart: bin/build
12 verbose stack Exit status 1
12 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
12 verbose stack at emitTwo (events.js:126:13)
12 verbose stack at EventEmitter.emit (events.js:214:7)
12 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
12 verbose stack at emitTwo (events.js:126:13)
12 verbose stack at ChildProcess.emit (events.js:214:7)
12 verbose stack at maybeClose (internal/child_process.js:915:16)
12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
13 verbose pkgid [email protected]
14 verbose cwd C:\Users\Adil Raza\Desktop\Intel Hackathon\charted
15 verbose Windows_NT 10.0.17134
16 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
17 verbose node v8.12.0
18 verbose npm v6.4.1
19 error code ELIFECYCLE
20 error errno 1
21 error [email protected] prestart: bin/build
21 error Exit status 1
22 error Failed at the [email protected] prestart script.
22 error This is probably not a problem with npm. There is likely additional logging output above.
23 verbose exit [ 1, true ]

I think it would be a nice addition if we could structure our source in a way that would move the data into separate charts automatically.

https://charted.co/c/46e0cd2

Thank you.

When a mouse is connected and there are 2-4 charts, the charts are first rendered with a scroll bar existing, and then the scroll bar goes away. The result is a space on right hand side where the scroll bar was.

I think there is probably a broader solution of refactoring how charts are presented, so that the PageController first figures out how all the charts should be displayed before rendering any of them.

I cloned and run npm install && npm start locally, the server run fine, but when I add a URL to load data, the page just refresh and not load anything.

See this in the console.

…so that if you have a few charts opened in tabs, it’s easy to disambiguate.

Hey all,

Thanks for this great project. It's super simple and looks fantastic.

Do you plan on implementing a "download chart" feature? A simple SVG or PNG would be nice. Or, perhaps even an embed feature to maintain interactivity?

I don't know if y'all planned to create something similar to Quartz/Chartbuilder but It would be nice to build these charts into products.

The embed code provided by charted.co is not rendered by the Medium editor.

I feel a little sheepish opening an issue here—this may more properly belong in a Medium Support channel—but I was hoping somebody here might know what's going on if it's an issue with this product.

Thanks!