-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Exposing ComponentFieldBindingObject
type for custom fields
#4657
Labels
👕 TypeScript
TypeScript typings issue
Comments
That is a reasonable ask, it should've been exposed since it is a public API. Should be up with the next release. |
This was referenced Jun 26, 2024
This was referenced Sep 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I'm most likely doing this wrong as I haven't found any documentation about it, so please show me the correct way if I am. I want to define a custom field by using the exposed
componentField
slot property that is in turn also exposed from the<Field>
component, so:Now I can see in the vee-validate.d.ts file that there is an interface called
ComponentFieldBindingObject
that defines the properties that would be needed in my custom component<CustomField>
, but the interface is not exported and therefore have to re-define my own.Describe the solution you'd like
Be able to use the vee-validate native
ComponentFieldBindingObject
interfaceDescribe alternatives you've considered
Define my own copy, which is no big deal but would be nice to use the native interface.
The text was updated successfully, but these errors were encountered: