Stanislav Lashmanov

> Needs to work with defineComponent aka outside of SFC. But how these typings are going to be useful outside of SFC? I thought that the main idea was to...

@yyx990803 what's the recommended way for plugin authors to support both Vue 2 and 3?

@yyx990803 I think people would also appreciate if Vue 3 docs had examples written both in JS and TS, where you could toggle between those two.

That'll be a breaking change for computed models with marginal gains in very specific scenarios, so for me it doesn't seem to be worth going the breaking path. Instead, you...

It does not introduce a custom attribute and is a syntax sugar for an existing object configuration for v-bind. That's why it said that users who use render functions won't...

What would `:[prop]` mean then? Dynamically assigned prop with dynamically assigned value?

> I find that untrue, in the following repro only the first char is displayed: https://codesandbox.io/s/v-model-decomposed-camel-case-84732 Thanks for pointing that out, this shows that current behaviour is inconsistent. For setup...

Yes, this is worth mentioning in RFC, I'll update it later accordingly. I didn't mention it beforehand because I was unaware that `setup` does not have this problem.

> Is it expected than even for setup(), the behavior is different for get/set and computed ? > > https://codesandbox.io/s/v-model-decomposed-camel-case-5ftt7 It is not, thanks for adding that! I'll update RFC...

Added a few more examples: * [`readonly` quick fix](https://github.com/CyberAP/rfcs/blob/fully-controlled-form-elements/active-rfcs/0000-fully-controlled-form-elements.md#fixes-poor-readonly-html-implementation) * [in-place uncontrolled bindings: ``](https://github.com/CyberAP/rfcs/blob/fully-controlled-form-elements/active-rfcs/0000-fully-controlled-form-elements.md#uncontrolled-bindings-still-possible) Also expanded Composition API section with current inconsistencies.