Add data-binding for yAxis

[sorin-davidoi]

Decided to remove the previous value for yAxis. However, this could remain and be extended by the user-supplied object.

[avdaredevil]

Any reason for this? What problem were you running into with this design?

[sorin-davidoi]

Maybe I'm missing something. I was trying to add a custom formatter for the Y axis, something like:

yAxis: { type: Object, value: {
          title: { text: null },
          gridLineWidth: 0,
          tickInterval: 25,
          maxPadding: 0,
          labels: { formatter: formatYAxisLabel }
        }},

[avdaredevil]

The API provided for this is:

app.$.myChart._chart.yAxis[0].update({
    type: Object,
    value: {
          title: {text: null},
          gridLineWidth: 0,
          tickInterval: 25,
          maxPadding: 0,
          labels: {formatter: formatYAxisLabel}
    }
})

Let me know if that does not work for you. I have a demo page reserved for pull requests, so I can put it as a demo.

[sorin-davidoi]

Thanks for the example. That works, but I feel that is exhibits a few drawbacks:

• accessing the underlying implementation is kind of a hack; the purpose of the web-component should be to hide the actual implementation
• the overhead of setting up an observer and calling update again if I want to change one of the properties
• taking extra care to check that app.$.myChart is defined (in my case, it is inside a dom-if template)
• inconsistency with the x-axis API

[avdaredevil]

Good points. Merging.