-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow use of a dataSourceUrl
(via ChartWrapper)
#121
Comments
I don't understand what you are referring to. Would you please please explain a little more or give an example? |
Straight from the above link referenced in the title
|
OK, thanks for the clarification. That's what I thought you meant, but I wasn't sure. |
dataSourceUrl
(via ChartWrapper)
I should mention that you are currently able to use a Sheets DataSource through a Query object. See here for more information. |
No problem, thanks for the info! -- Honestly I would much prefer to see full chart type suite supported over this feature... This was just a surprise when I was trying to setup a demo for some co-workers. As for the QueryObject, I saw that, but was not sure how (or if it could be) to integrate it with the Web Component usage, granted for my purpose, I did not devote a lot of time to it due to the nature of my immediate need. |
Yeah, for sure the DataSourceUrl should be supported. It's usage is extremely similar to the data URL in the component know but has huge fundamental differences. I'm definitely interested in twisting this element around to look almost exactly like the API for a ChartWrapper soon. |
I've created a PR that adds a Query element. <google-chart-query url="..." data="{{data}}">
<google-chart data="[[data]]"> |
As seen here: https://google-developers.appspot.com/chart/interactive/docs/reference#chartwrapperobject
Maybe its not expected to, but the assumption was, it mentions URL support for the Chart API and that was a URL for the chart API.
It would be nice if it could be supported though.
The text was updated successfully, but these errors were encountered: