How to check if field is required using useField?

[SimmeNilsson]

Is your feature request related to a problem? Please describe.
I have a custom component that is using useField internally.
It renders both label and input element.
I would like to add a * to the label text if the field is required.
Is there some way I can figure out if this field is required (for example if yup.required was used on the field in the schema)?

Describe the solution you'd like
It might already be available, only that I haven't found it.
But I would like to look at something from useField and be able to figure out if this field is required or not.
Without having to pass a property to my component for it that might get out of synch with the schema if someone makes code changes.

Describe alternatives you've considered

I've searched for it in meta from useField.

Passing a boolean property to my component.
But I would like to use the name connection to avoid the "required flag" travelling another path (view model -> view -> component prop vs useField) to avoid mistakes.

[logaretm]

I moved this to discussions since it is a question more than an issue.

At the moment, vee-validate v4 doesn't have a concept of special rules like required in v3. Meaning it is up to you to build the API that would allow you to figure that out. The reason for that change was opening vee-validate up tp multiple rules providers like yup, zod and more.

[SimmeNilsson]

I understand.

In knockout-validation we were able to access the rules and examine them through a property on the observable.
Locate the required rule and check if it was enabled.

Is there some (futureproof) way to access the rules for inspection from useField?

[davidreyg]

@SimmeNilsson any news on this topic? 🗡️

[SimmeNilsson]

@davidreyg After some digging into source code for both vee-validate and yup I went for a solution for that particular combination only.
Digging up the yup schema and checking for required rule. It works in the basic cases including conditional required.
However, there are cases with object lists that I'm unable to get to work due to the output from yup.describe.
See here for more information.