Update documentation for v3

v3 syntax is really different from v2 syntax and the docs don’t quite reflect this.

In all the docs under Axes, it’s not stated what options are available for scaleId, for instance, in the context of options.scales[scaleId].ticks

Please resolve this by stating that scaleId could be x or y (or whatever other options are available)

[kurkle]

No, its not actually wrong. You are free to use any valid key as scaleId. If there is no scale config, defaults will be x and y (or r), but if there is, first id for axis is used. There are some “magic” rules to define the axis of a scale, its taken from the first letter, unless specified by the axis or position option.

This is valid for example:

options: {
  scales: {
    sales: {
      position: 'right',
      type: 'linear'
    },
    time: {
      position: 'bottom',
      type: 'time',
    }
  }
}

[sugoh]

No, its not actually wrong. You are free to use any valid key as scaleId. If there is no scale config, defaults will be x and y (or r), but if there is, first id for axis is used. There are some “magic” rules to define the axis of a scale, its taken from the first letter, unless specified by the axis or position option.

This is valid for example:

options: {
  scales: {
    sales: {
      position: 'right',
      type: 'linear'
    },
    time: {
      position: 'right',
      type: 'time',
    }
  }
}

This is a great feature! Could you add what you just described to the docs?

I’m not the only one who encountered the same roadblock. For instance, it would specifically be helpful if the docs identified [x/y] as the default scaleId before going on to explain what you just mentioned.

Feel free to close this thread whenever you want. I don’t have anything further to add.