Stanislav Lashmanov

I would argue that it is not more flexible, but quite the opposite. If we want to watch multiple sources: ```html ``` ```js const fields = reactive(['foo', 'bar']) const handleEvent...

> Say I want to dynamically add or remove a listener for properties. How are you gonna do that? This is what I meant when I said the other solution...

If we use an `update:` prefix we get the desired behaviour out of the box, but these events are reserved for `v-model` and I would like to avoid confusion here...

I think adding a special case of a `change:` event prefix is a good enough trade-off. If the goal is to have both versatility and at the same time leave...

But your template code is actually 136 lines long. That's not a lot for such a component. The largest part of your SFC is CSS, which should be imported from...

> Ref #21 Thanks for linking a related issue. I knew someone has already proposed that! But there are some key differences from the #21 proposal that I'd like to...

> But this RFC is only approaching the problem with the idea of not creating a breaking change instead of comparing the two existing solutions and why one would make...

> how much is it worth, when in some other common vue practices HTML/XML consistency is not followed either (case-sensitive v-on, PascalCase tag names). Consider this: when we do not...

How would you type slots that depend on props?

If this is primarily a TypeScript type hinting wouldn't it be better to export slot typing separately? ```html export type slots = { default: { message: string } } ...