#4181

[zaalbarxx]

#4181

🔎 Overview

extended list of exposed data for Field.ts to include field's value, meta and errors, would allow for creating custom component for "grouping" fields state

🤓 Code snippets/examples (if applicable)
https://stackblitz.com/edit/vue-3-veevalidate-form-validation-example-4159qg?file=src%2Fvee-validate.esm.js,src%2Fmain.js,src%2FFieldGroup.vue,package.json,src%2FField.vue,src%2FApp.vue

✔ Issues affected
closes #4181
-->

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (3130470) 97.32% compared to head (0180150) 97.32%.

❗ Current head 0180150 differs from pull request most recent head 6502957. Consider uploading reports for the commit 6502957 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4553   +/-   ##
=======================================
  Coverage   97.32%   97.32%           
=======================================
  Files          86       86           
  Lines        6762     6770    +8     
  Branches     1253     1253           
=======================================
+ Hits         6581     6589    +8     
  Misses        181      181           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[logaretm]

Thank you for the contribution!

While I do not prefer this pattern, I no longer see the harm in having this since it is in the Vue docs.

However, you should be aware of this doc note:

refs are automatically unwrapped just like on normal instances

That means the types here are wrong, no? Because it is a direct cast instead of inferred unwrapped ref.

In your PR, this is what is suggested to access the field value:

So it's going to be fieldRef.value.value.value.

But in practice, it gets unwrapped:

So it's only fieldRef.value.value.

So let's get those types corrected and I will be happy to approve this.

[zaalbarxx]

Should be correct now ? @logaretm

[logaretm]

All good, thank you.