Eduardo San Martin Morote
Eduardo San Martin Morote
[Fixed upstream](https://play.pinia.vuejs.org/#eNqNVF1v2jAU/StWXqAq2K3YuolRRFf1oXvYpnVvyx5CcgG38YdshyKh/Pdd2yEEaCekKHKu7zk+917nbJM7rem6gmScTGxuuHbTVHKhlXFkSyoL96qSDsyTUwZITRZGCdKjLI/hXidZZPrJZQ4GfnWXO66kbRGaS571vqQSNiG9gEVWlQhLJSG5ErpyUIzjJ6GU7sj6RxIG5E8vnN37e+Fz64F/C3ArVdgdviFoNLxFwWVuQMCeJpX4TFjbAvxwIHSJEvCLkImebrcoFGlIXU+YjtF55ZySZJaXPH+5TZOWN02mj7v1hMU0hExYy5oMkti6IUqlz1ZJnEHQjzRhw6ZJW1GahA76SJqwsKZgxXBu1KsFg/g0Ca3wqTMcKCtg7ZQq7TDTPMJWzmk7ZiwvJOYXUPK1oRIck1qwE8zsht7Qa1byOcODGJcFbA6PQcSwAHEO+y51dkWvP9BPgXU9akjFMeu5cg1OgwtkVmI2oh/pZ1Zw67rh93vk8RhcgxkaQBkGzLnHHsG6Rx9tnRy/u2s4fGdzJRd8eTR6/y/wEswPHS7vwRXIylK9fgsxZypoa8lXkL+8EX+2m1jTTwNBWad+l5kl4DX12w9P32GD63ZTqKIqmzG8s/kLrCorrzGmfa1kgbI7eUHtY7jJXC5/24eNA2l3RXmh+x84zOP+P6Xv5Y7oqNPFxoeos9jC1orQXbiEQ8+KDuT/7MaCsP3WnVjcbRfcj16DPjeIUqz3pDHpX5DbKek3hjAmV6S+CHVk0XJa4a0fIKIJEeJW3NKAvLyMsdgE/67RjpL6H4QU5K8=)
Tell me if you need help to upgrade to Vuefire 2, the only thing that changed were installation instructions: https://vuefire.vuejs.org/vuefire/getting-started.html#installation
Also at https://github.com/vuejs/vue/issues/7943
Give https://v3.vuejs.org/api/refs-api.html#customref a look. It's not really clear what is wrong with a boiled down example of what you are trying to do. You might want to provide one.
I agree on not relying on order to decide the outcome of combining `v-bind` with a regular attribute. But this RFC is only approaching the problem with the idea of...
Wouldn't it be better to add it to `attributes.json` for Vetur so it doesn't bloat the final bundle?
Transferred to RFCs to follow its process
This was asked for before at https://github.com/vuejs/vue/issues/4956 Same for implicit prop values https://github.com/vuejs/vue/pull/2877 Given the existing syntax for directives (like `v-bind`) this introduces a custom attribute named `class:property` (property being...
I would say something along the lines of _origin_ for the prop instead of `gravity` would make more sense given the possible values
Instead of using `beforeRouteEnter`, using a [Data Loader](https://uvr.esm.is/data-loaders/) would be the preferred approach now. You can return any data you want rather than changing the component instance which creates coupling...