@simoncomputing/mui-bueno-v3 0.1.18 → 0.2.1

package/README.md

@@ -41,7 +41,7 @@ In the application repo:
 
 ```shell
 # Update package to look for this file in the proper directory.
-npm i ~/git/mui-bueno-v3/simoncomputing-mui-bueno-v3-0.1.18.tgz
+npm i ~/git/mui-bueno-v3/simoncomputing-mui-bueno-v3-0.2.1.tgz
 
 # Install
 npm install

package/dist/components/Form/MForm/MForm2.d.ts

@@ -54,7 +54,7 @@ import * as React from 'react';
  *
  * **Owned mode**
  * - pass `defaultValues: DefaultValues<T>` (required)
- * - optionally pass `resolver`, `useFormProps`, `reinitializeKey`, etc.
+ * - optionally pass `validationSchema` (Yup) and/or `resolver`, `useFormProps`, `reinitializeKey`, etc.
  *
  * ## Default values (source of truth)
  * MForm2 does not define its own default values. It forwards props to `MFormProvider2`, which chooses:

package/dist/components/Form/MForm/MFormProvider2.d.ts

@@ -1,4 +1,5 @@
 import { DefaultValues, FieldValues, Resolver, SubmitErrorHandler, SubmitHandler, UseFormProps, UseFormReturn } from 'react-hook-form';
+import { AnyObjectSchema } from 'yup';
 import * as React from 'react';
 /**
  * # MFormProvider2 Documentation
@@ -9,7 +10,7 @@ import * as React from 'react';
  * - Standardizes submit behavior (including optional Axios 422 → field error mapping).
  * - Supports two modes:
  *   - **Controlled**: you create the RHF methods with `useForm()` elsewhere and pass `methods`.
- *   - **Owned**: this provider calls `useForm()` internally using `defaultValues`/`resolver`.
+ *   - **Owned**: this provider calls `useForm()` internally using `defaultValues`/resolver.
  * - Optionally exposes a programmatic submit function via:
  *   - `submitRef` (imperative ref),
  *   - and/or an internal context + `useMForm2()` hook.
@@ -47,15 +48,16 @@ import * as React from 'react';
  * - You need `methods` in the parent component (e.g., `useFieldArray()` at the dialog level),
  * - You want to configure RHF outside of the wrapper.
  *
+ * Note: in controlled mode, `validationSchema` is not accepted because the resolver must be configured
+ * when you create `methods` via `useForm({ resolver: ... })`.
+ *
  * ### Owned mode
- * You provide `defaultValues` (and optionally `resolver`, `useFormProps`, etc.):
+ * You provide `defaultValues` (and optionally `validationSchema`, `resolver`, `useFormProps`, etc.):
  * ```ts
- * <MFormProvider2 defaultValues={...} resolver={...} onSubmit={...}>{...}</MFormProvider2>
+ * <MFormProvider2 defaultValues={...} validationSchema={...} onSubmit={...}>{...}</MFormProvider2>
  * ```
  *
- * Use this when:
- * - You want a very simple call site,
- * - You don’t need to share methods with a parent component.
+ * Owned mode is the recommended path when you want minimal call-site configuration.
  *
  * ## Error mapping (Axios 422 → RHF errors)
  *
@@ -203,6 +205,15 @@ export type MFormProvider2ControlledProps<T extends FieldValues> = CommonProps<T
  */
 export type MFormProvider2OwnedProps<T extends FieldValues> = CommonProps<T> & {
     defaultValues: DefaultValues<T>;
+    /**
+     * Yup schema for validation (owned mode convenience).
+     * If provided and `resolver` is not provided, the provider will use `yupResolver(validationSchema)`.
+     */
+    validationSchema?: AnyObjectSchema;
+    /**
+     * Explicit resolver override.
+     * If provided, it takes precedence over `validationSchema`.
+     */
     resolver?: Resolver<T>;
     shouldFocusError?: boolean;
     useFormProps?: Omit<UseFormProps<T>, 'defaultValues' | 'resolver' | 'shouldFocusError'>;