Thorsten Lünborg

@FranzSkuffka The new stuff won't replace awesome-vue. They fill different needs/purposes. awesome-vue is a collection about everythign vue-related. IT's godd fore that pupose, but hard to maintain any kind of...

We will probably be using github as a DB for the curated list. We probably won't do that for awesome-vue because maintaining such info will probably be too much work....

@ryandeussing ember observer is pretty awesome, and we are indeed working on something very similar.

Currently not, because we are still playing around with a few options to decide how to set this up from a technical pov. Once we have decided how to set...

`toRef()` works as expected. The prop is possibly undefined, so the generated ref possibly contains and `undefined` value: `Ref`. The propblem is only with `toRefs()` For `toRefs()`, this is a...

> But, I think, the main topic of this issue is that it is impossible to separate Ref from Ref If you have an optional prop (= it can be...

> This is only valid for `props`, but `toRefs` is used in on the user land, I believe the current `toRefs` definition is accurate for the type coming from `defineProps`....

@pikax you sure? I think what OP tries to do here would require casting or a new ref. They are checking for .value to not be nullish, but that will...

Yeah thats what i meant, basically.

well, then create a computed property that returns the default string if the optional prop is undefined. that then will also always be a string. One way or another *you*...