Q: Global configuration for useField/useForm?

[sschneider-ihre-pvs]

there is configuration but it is mainly for configuring components.
How do I archive that for a useForm so I don't have to handle all fields manually? For example if I only want to validate on blur

[logaretm]

The configuration is mostly for components given how messy it is to configure stuff every time in templates. Besides, there is nothing to configure for the composition API aside from validateOnMount and a few other things because you will have to bind the handlers anyways to your inputs.

But from a re-usability aspect, with the composition API you have plenty of options:

You can put the most common configs in an object and re-use as necessary.

export const defaultConfig = {
  validateOnMount: true,
  // other stuff
};


// somewhere in your code
import { defaultConfig } from './whatever';

const field = useField('fieldName', rules, {
  ...defaultConfig,
  // other local config
})

You can build an higher-order function that applies the config over useXXX from vee-validate

const globalConfig = {
  validateOnMount: true
};

export const useFieldWithConfig = (field, rules, config) => {
  return useField(field, rules, {
    ...globalConfig,
    ...config,
  })
}

[sschneider-ihre-pvs]

The thing is, if you want to skip useField in favor of useForm it is not that easy. I have rather large forms so throwing in a schema for the form is easier than declaring every single field on its own. Also it seems that bails kicks in also in useForm so it stops on the first validation error.

[brendomaciel]

I agree. I use useForm a lot and it would be nice to have a way to define the configs per form as well.