apollo VS vee-validate

Is this what apollo-components is all about? https://github.com/vuejs/apollo Bulletproof is based on a REST API, so if GraphQL is the backend, this would be a great choice!

If you're set on using both Nuxt 3 and Vue Apollo, I'd recommend not using the Nuxt Apollo module, and instead integrating Vue Apollo directly: https://github.com/vuejs/vue-apollo

Cool, if you do go with graphql, I'd recommend vue-apollo on the client end. Combine with @vue/apollo-composable and graphql-codegen and it feels like sorcery.

Frontend is vuejs 2 that was scaffolded with vue-clu and is a CRUD site for the backend. I planned on using vue-apollo for the frontend to easily connect to graphql backend, I was especially excited to learn that vue-apollo handles most of the state and caching and decided to try it instead of vuex for state. I've hit a couple snags though and am beginning to think that vue-apollo isn't the right way to approach this (plus their documentation leaves much to be desired). Here's where I'm at:

You might have heard lots of buzz around GraphQL, and if you are interested in integrating it with Vue.js, then I would like to suggest you try Vue Apollo. The library makes use of Vue in the combination of GraphQL/Apollo for a smooth as well as a pleasant experience. To get startedClick here

I'm learning GraphQL and every tutorial/vid I look at in relation to using Apollo with Vue seems to involve this other package, graphql-tag. But no one ever seems to explain why it's needed, and it's not listed as a dependency of Vue Apollo. So can anyone tell me precisely why graphql-tag is needed, and whether Apollo can work with Vue without it? Essentially, is it required (and if so why isn't it listed as an Apollo dependency?) or optional?

The Vue ecosystem is packed with many great form validation libraries, VeeValidate, Vuelidate, and FormKit just to name a few.

The two I heard of are Vuelidate and Vee-validate. Any opinion? Thanks.

Sorry if this comes off harsh. I think having a collection of built-in validators are nice, but there's also very solid libraries like Zod or Yup that have that feature nailed down. In the end, I don't feel like this library does all that much to justify it's existance in the vanilla case and especially in the Vue case. Here's some specific criticisms that I think would improve the library, though even if these items were fixed I would feel like it's pretty far off from being as helpful than existing libraries, e.g. vee-validate for Vue which allows for dynamic field generation while also supporting validation through Yup allowing for more complex cross-field validation.

VeeValidate

Ever used vee-validate? It is a nice form validation library and now with the help of composition API got even stronger.

You could try looking into VeeValidate, as it's probably the most similar in terms of hook usage.

I use VeeValidate for form validation. Is there any plugin or built-in feature in Quasar for replacing this package?

Validating forms helps authenticate processes faster. Using vee-validate, you can validate the user's data inputs in a minimalistic and straightforward manner (e.g., checking the validity of emails, passwords, etc.). 🗃 The library works with most of your favorite UI components and native HTML elements. Moreover, the built-in rules are laid out in 45+ locales. 🚩