Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validating 3rd Party Libraries #3262

Closed
donPuerto opened this issue Apr 13, 2021 · 5 comments
Closed

Validating 3rd Party Libraries #3262

donPuerto opened this issue Apr 13, 2021 · 5 comments
Labels
📚 docs documentation related

Comments

@donPuerto
Copy link

donPuerto commented Apr 13, 2021

Is your feature request related to a problem? Please describe.

Do we have "Validating 3rd Party Libraries" aka how to use this library to other frameworks?
ie Quasar now is in beta,

  • Example for component base
  • Example for composition api
@logaretm logaretm added the 📚 docs documentation related label Apr 15, 2021
@logaretm
Copy link
Owner

I assume you are talking about v4, I haven't gone through that because most libraries are still in beta.

let me know if some UI library is stable enough and I will add examples for them

@donPuerto
Copy link
Author

Yes V4. Quasar is much stable already even it is in beta.

@logaretm
Copy link
Owner

I have added a simple example for both quasar and element plus, should be up soon in the examples section

@donPuerto
Copy link
Author

Thanks mate

@jdriesen
Copy link

jdriesen commented Jul 8, 2021

Any news on this subject ?
(integration of vee-validate in Quasar v2)

Maybe an example available ?
(more in particular... what has to be the content in vee-validate.js in the boot folder of Quasar)
Please don't forget about i18n :)

Thanks in advance for any reply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📚 docs documentation related
Projects
None yet
Development

No branches or pull requests

3 participants