Stories rework: VaValue

[xiongmao86]

Story rework of VaValue.
Part of #3676.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Improvement/refactoring (non-breaking change that doesn't add any feature but make things better)

[xiongmao86]

I am very sorry that I forget to remove reluctant import, the pr is ready now.

[asvae]

Hey. Thanks!

We probably don't need last 2 stories (leave only Defaul), as VaValue component doesn't introduce any DOM.
@m0ksem what do you think?

For first story it would be nice to have interaction test (you can check bactop for examples).

[m0ksem]

Hey. Thanks!

We probably don't need last 2 stories (leave only Defaul), as VaValue component doesn't introduce any DOM. @m0ksem what do you think?

For first story it would be nice to have interaction test (you can check bactop for examples).

I should've been moved two last stories to docs demo (or I actually did it). Since we moved to stories from demos, I think we can remove two last stories.

We can add story of usage VaValue with reactive object, not just boolean.

<VaValue :defaultValue="{ name: '', age: 0 }" #default="v">
	<VaInput v-model="v.name" label="name" />
	<VaInput v-model="v.age" label="name" />
</VaValue>

I'm not sure if reactive object will work, but we need a story about it.

[xiongmao86]

Thanks, @asvae, @m0ksem. I don't know how to check whether the reactive object case work. Is this commit ok?