Eduardo San Martin Morote

I don't know if there will be a way to inject things to context but the `router` can be directly imported and it gives access to `currentRoute` (which is currently...

This has been discussed previously in multiple issues, one of them is https://github.com/vuejs/vue/issues/8049. By looking at the download stats of [the package that implement such behavior](https://www.npmjs.com/package/vue-coerce-props), we can see that...

> @posva the package you mentioned does not look nearly as satisfying as the proposed feature. The only thing missing is being able to rename the prop, which is the...

> Its not about what is missing in the package, Its about API design It's about more than that to be fair but the API could be the same if...

The `.value` is necessary and described at https://vue-composition-api-rfc.netlify.com/#ref-vs-reactive This was largely discussed during the RFC process at https://github.com/vuejs/rfcs/pull/78 and the previous one at #42 (that's why it has a note...

Not sure why this was open so long… These use* methods should be (and currently are) exposed by the corresponding libraries @matthew-dean FYI, in case you missed, native inject also...

I don't think an extra syntax here is worth, this looks like a very niche case. Even with dynamic components, it's okay, although it's clearly something that will look better...

If you are interested, I implemented a store version that works well with the Composition API. It's still open in terms of API design and has devtools, typescript, and plugin...

Closing as this _functional api_ can be achieved with setup stores in [pinia](https://github.com/vuejs/pinia)

I think that as long as we can **ensure key order in objects** across all browsers, this is feasible and it aligns with function usage: ```js // both work function...