Naming of database-specific options inconsistent

[jachstet-sea]

I'm trying to create a line chart using Chart.js v2.0.2 where no dataset has data points displayed but one. So I set these options in the global chart settings:
elements: {point: {radius: 0, hoverRadius: 0, hitRadius: 0,},},

Then for the dataset I want to have the points displayed I have to use:

{
        label: "My Third dataset",
        data: [randomScalingFactor(), randomScalingFactor(),],
        yAxisID: "y-axis-3",
        fill: false,
        radius: 5,
        pointHoverRadius: 5,
        hitRadius: 8,
}

This works but what one can see here is that the options "radius" and "hitRadius" do not have the "point"-prefix, but "hoverRadius" does. As a question: do "radius" and "hitRadius" affect other elements despite points?

In the example in the docs (https://nnnick.github.io/Chart.js/docs-v2/#example-usage), most of the options are prefixed with "point".
The option "tension" which can be set per-database as well is not prefixed with "line".

What is your opinion about this inconsistency? Use prefix for all options or for none? I can work on the code and create a PR if there is a consensus.

[etimberg]

@jachstet-sea those names are definitely inconsistent. I think the prefixes are fine for the line chart and we should make radius into pointRadius. I'd be happy to merge a PR for this. Please ensure that setting radius will still work ... we don't want to break any existing charts. Same thing applies to the tension property.

[etimberg]

Fixed in #2314