Andrew Talbot

@LinusBorg I see you were assigned to review. Any thoughts?

I'm all for @ycmjason's idea (https://github.com/vuejs/rfcs/issues/96#issuecomment-552822532). That seems easy to support, easy to optimize, and very similar to how you would approach the issue if you were writing JSX. ---...

This seems related to https://github.com/vuejs/rfcs/pull/140 and https://github.com/vuejs/rfcs/pull/175 (which I see you've mentioned already in https://github.com/vuejs/rfcs/issues/156). I might think about this differently, as I wouldn't intuitively think an array should mutate...

I like the idea. But, I'm also unsure about it because `v-click-outside` is just one additional character than `@click.outside` and actually reflects better what is happening behind the scenes (it's...

@jods4 you're last comment is interesting. Do you think it might make more sense to provide a basic building block then, like a `v-outside` directive that attaches an event listener...

@beeplin Good question. I've been wondering whether, when using this new API, it is preferable to use everything as a hooks: ``` const { route, router } from useRouter() console.log(route.params.id)...

I would expect to do it the way @skyrpex has it. That works well enough if the goal is simply sharing prop definitions. In the case of hooks and props,...

I did misunderstand. Seeing that example helped, thanks. It definitely seems to fit the design of the rest of the API. I also think are right about props of the...

I don't disagree on some points, but I am also unsure if one or the other is better. I personally like the ref API as it is, but I'll admit...

I like this pattern. A few thoughts: 1. I wouldn’t want to return bindings of state because then it can be mutated from elsewhere. I would expose with some readonly...