I'm not sure if this is a code bug, or a documentation bug, but after spending the better part of a day dealing with vague error messages I thought I should report it. Apparently if you specify google-chart tag attributes using double-quotes, exceptions will be thrown. For example, if you specify options using
<google-chart options="{'title': 'Distribution of days in 2001Q1'}"
cols="[{'label':'Month', 'type':'string'}, {'label':'Days', 'type':'number'}]"
Most people use " for attributes as this is the HTML and XML standard and it's what we're used to. However, in this case apparently the attributes are converted into JSON and single ticks around a key or value (inside the options/cols/rows attributes) cause parsing problems.
Could you update the documentation to explicitly state (in bold or otherwise) that the attributes must be specified "exactly as they are in the documentation", and explain the double- vs single-quote problem.
I'm not sure if this is a code bug, or a documentation bug, but after spending the better part of a day dealing with vague error messages I thought I should report it. Apparently if you specify google-chart tag attributes using double-quotes, exceptions will be thrown. For example, if you specify options using
Most people use " for attributes as this is the HTML and XML standard and it's what we're used to. However, in this case apparently the attributes are converted into JSON and single ticks around a key or value (inside the options/cols/rows attributes) cause parsing problems.
Could you update the documentation to explicitly state (in bold or otherwise) that the attributes must be specified "exactly as they are in the documentation", and explain the double- vs single-quote problem.