You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/docs/docs/api-reference/form-props.md
+26-3Lines changed: 26 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,8 +91,8 @@ The signature and documentation for this property is as follow:
91
91
##### computeSkipPopulate <T = any, S extends StrictRJSFSchema = RJSFSchema, F extends FormContextType = any>()
92
92
93
93
A function that determines whether to skip populating the array with default values based on the provided validator, schema, and root schema.
94
-
If the function returns `true`, the array will not be populated with default values.
95
-
If the function returns `false`, the array will be populated with default values according to the `populate` option.
94
+
If the function returns `true`, the array will not be populated with default values.
95
+
If the function returns `false`, the array will be populated with default values according to the `populate` option.
96
96
97
97
###### Parameters
98
98
@@ -104,7 +104,6 @@ A function that determines whether to skip populating the array with default val
104
104
105
105
- boolean: A boolean indicating whether to skip populating the array with default values.
106
106
107
-
108
107
##### Example
109
108
110
109
```tsx
@@ -252,6 +251,30 @@ render(
252
251
);
253
252
```
254
253
254
+
## experimental_customMergeAllOf
255
+
256
+
The `experimental_customMergeAllOf` function allows you to provide a custom implementation for merging `allOf` schemas. This can be particularly useful in scenarios where the default [json-schema-merge-allof](https://github.com/mokkabonna/json-schema-merge-allof) library becomes a performance bottleneck, especially with large and complex schemas or doesn't satisfy your needs.
257
+
258
+
By providing your own implementation, you can potentially achieve significant performance improvements. For instance, if your use case only requires a subset of JSON Schema features, you can implement a faster, more tailored merging strategy.
259
+
260
+
If you're looking for alternative `allOf` merging implementations, you might consider [allof-merge](https://github.com/udamir/allof-merge).
261
+
262
+
**Warning:** This is an experimental feature. Only use this if you fully understand the implications of custom `allOf` merging and are prepared to handle potential edge cases. Incorrect implementations may lead to unexpected behavior or validation errors.
0 commit comments