fix: emit date change event to match React

[davidnixon]

Contributes to #1625

What did you do?

• some minor eslint-style changes to the story to put @ items at the end of the attribute list i.e. @change="onChange"
• some minor tidying of controls on stories
• add new emit for dateChange this event mimics the change event in the Carbon React
• separate the v-model stories for a single kind and range kind. The v-model is different for each of these and I think separating the stories makes it a bit clearer.
• for single kind and range kind stories, show the dateChange in the actions tab

Why did you do it?

See #1625 but basically there was no way to listen for changes for a range style date picker.

How have you tested it?

Via the storybook

Were docs updated if needed?

• Yes

[davidnixon]

The change event is unchanged. It still emits a native change event for the underlying input. This is used for kind simple and short.

The change event is still emitted for kind single and range but ti is not shown in the storybook.

[davidnixon]

For kinds single and range the new dateChange event is emitted. The param passed to the event is an array of Date objects. For a kind single this array has 1 entry. For a kind range, the array has 2 entries.

[davidnixon]

For a kind range, the array has 2 entries.

[davidnixon]

@gabisinhas
Can you have a look at this one and lmk. I did consider changing the change event but that would potentially break anyone who is currently using that event. That's why I decided on the dateChange event.

[gabisinhas]

@davidnixon i think it might resolve this. If you can publish then I can test it. thanks for the attention to this issue.

[davidnixon]

carbon-vue-3.0.20-1abc8.tgz

npm remove @carbon/vue
npm add carbon-vue-3.0.20-1abc8.tgz