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

[Feature Request] Expose validated inputs present in forms #19365

Closed
charlesg99 opened this issue Mar 10, 2024 · 2 comments · Fixed by Enterprise-CMCS/cmcs-eregulations#1307 · May be fixed by Shuunen/ging#200
Closed

[Feature Request] Expose validated inputs present in forms #19365

charlesg99 opened this issue Mar 10, 2024 · 2 comments · Fixed by Enterprise-CMCS/cmcs-eregulations#1307 · May be fixed by Shuunen/ging#200
Assignees
Labels
C: VForm VForm T: enhancement Functionality that enhances existing features

Comments

@charlesg99
Copy link

Problem to solve

Please expose the actual vinput associated with the validation in the v-form "items" array. Atm we only have acces to its id and validation state. In vuetify 2, a form would include all vinput vnodes in its "inputs" array, which was very convenient to track all vinputs present in the form, no matter their hierarchy. This feature was lost in vuetify 3.

Proposed solution

When the validation registers to its parent form(s), include a reference to the actual vinput vnode instead of its uid only. So each item in the vform's "items" array would have an additionnal property that would be the actual vinput vnode.

@KaelWD
Copy link
Member

KaelWD commented Mar 12, 2024

What is the use case for this? "Please do this" isn't a problem.

@charlesg99
Copy link
Author

charlesg99 commented Mar 12, 2024

As I said it was convenient in vuetify 2 since it was possible to access all the inputs no matter their nesting levels. In a parent component containing a form, where "form.validate" and such would be called, it made it possible to check custom properties set on each input nested in the form.

#19282

This isn't a problem per se, that's why it is a feature request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment