Replies: 1 comment 2 replies
-
What used to set Vue apart from all other frameworks was the Options API. It forced your components do be organized. While this is not important in small projects, this is a huge thing in large, corporate systems. The fact it became a second-class citized, with poor TypeScript support, is very unfortunate. Composition API becomes a mess really quickly. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Vue3 has defaulted to setup for a while now ( see the reasons )
I think it's time for Pinia to do the same to keep up with similar sintax and familiarity for someone learning vue3 and wanting to add stores to their project.
Related to #1265 - this was 2 years ago, much have changed since then
The "While Composition API is not for everyone" is outdated (and this phrase should be removed from the docs). Every new developer entering the Vue ecosystem will default to setup (composition API) and learning Pinia will be a pain point.
Let's change this and make
<script setup>
default for Pinia docs and hideoption api
under a toggle.Beta Was this translation helpful? Give feedback.
All reactions