chore: remove log

docs/src/pages/guide/composition-api/getting-started.mdx

@@ -80,9 +80,11 @@ For example, if you have a field called `email` in the form context, the field p
 ```ts
 const { defineField } = useForm();
 
-const email = defineField('email');
+const [email, emailAttrs] = defineField('email');
 ```
 
+Note that `defineField` generates a pair of values, the first one is the value model and the second one is the attributes/props object. The props object contain attributes or event listeners that are useful to have on the input control or component which enables custom validation triggers and more.
+
 Here is a basic example of how to use `defineField` with a simple input element:
 
 <Repl files={{ 'App.vue': 'CompositionInputBindsBasic01' }} client:only />
@@ -139,8 +141,6 @@ Notice that for components, validations are executed immediately. This is intend
 
 ### Mapping attributes and props
 
-You have noticed in the previous examples that `defineField` generates a pair of values, the first one is the value model and the second one is the bindings object. The bindings object contain attributes or event listeners that are useful to have on the input control or component.
-
 But aside from the attributes and listeners that vee-validate adds to those binding objects, you can also map the attributes and props of the in. This is useful when you want to:
 
 - When you want to map the attributes/props to a different name.

packages/vee-validate/src/useForm.ts

@@ -946,7 +946,6 @@ export function useForm<
     config?: Partial<InputBindsConfig<TValue, TExtras>> | LazyInputBindsConfig<TValue, TExtras>,
   ) {
     const label = isCallable(config) ? undefined : config?.label;
-    console.log(label);
     const pathState = (findPathState(toValue(path)) || createPathState(path, { label })) as PathState<TValue>;
     const evalConfig = () => (isCallable(config) ? config(omit(pathState, PRIVATE_PATH_STATE_KEYS)) : config || {});