Interaction axis options default in the samples is not xy

[stockiNail]

Default interaction options in the samples are set to 'x' instead of 'xy' as expected.

chartjs-plugin-annotation/docs/scripts/defaults.js

Lines 9 to 13 in 70078cc

	interaction: {
	mode: 'nearest',
	axis: 'x',
	intersect: false
	},

[kurkle]

Why is xy expected?

[stockiNail]

Well, because the samples, where the events are showed, seem to me to be implemented assuming there is axis: xy and not other axis options. Maybe I'm wrong and I can change the title, removing it.
The samples was developed where interaction wasn't implemented and then axis was XY and mode nearest even if not declared.

[kurkle]

🤔 I only see one sample that this affects, maybe I'm wrong. But instead, it would be better to fix that 1 sample and also create new samples demonstrating how the different interaction modes can be used in this plugin.

[stockiNail]

Ok, doable. Nevertheless, my opinion as user, I'm expecting to go to the samples and to have the default chart options (in this case interaction is not) because if I'm adding the interaction to the sample, it seems the user should always do. But that's my point of view and maybe I'm wrong. Anyway, let me change the PR following your hint.

[kurkle]

In that case the defaults override should be removed

[stockiNail]

That's the best solution for my perspective. But I don't want to force you to accept it if you have some doubts.

[kurkle]

I'm ok removing the defaults and setting in the samples where required. Its better that way. I think the current defaults are to make the charts work in an opinionated way, which is not good.

[stockiNail]

I'm ok removing the defaults and setting in the samples where required. Its better that way. I think the current defaults are to make the charts work in an opinionated way, which is not good.

Already done

[stockiNail]

About additional sample... to show events, you need a console (I have seen there is already a sample). In my lib showcase, I use checkbox to enable and disable options in order to enable the user to see the different behaviors with different options. Here, correct if I'm wrong, you can use only buttons.

[kurkle]

Yes, at least you need to use a button to trigger an change. I think you could use normal html elements and query their values in the action, but not sure if that is worth the effort.

[stockiNail]

Yes, at least you need to use a button to trigger an change. I think you could use normal html elements and query their values in the action, but not sure if that is worth the effort.

OK, let me close another issue, related to hide some elements methods and then I'll do an event sample