Usual excluded props in custom components,
Using a subset of SchemaNode since decoration happens only at the construction of the schema and dynamic values don't retrigger decorators for performance and dependency reasons.
Used to defines properties of a function without the usual schema node props This is usefull to know what properties are expected from a library consumer point of view
Function representing the schema validator with {name: "Format", ...}
options use that interface
interface FormatValidatorOptions {
// Valid javascript regex pattern without the surounding slashes ie: "[a-z]"
format?: string;
// normal RegExp flag
flags?: string;
}
example of schema
{
"name": "Format",
"format": "0x[a-f]{8}",
"flags": "gim"
}
Ask yourself if you really should check for this this is a utility for the consumer code to understand which repository is being used to render forms. As there was many clone versions, all with similar structures some utilities were polymorphic dealing with the slight API discrepancies using that function
Function representing the schema validator with {name: "Length", ...}
If a value is defined, it tests the content's length based on an optional minimum and/or optional maximum
Function representing the schema validator with {name: "Presence", ...}
If a value is undefined it returns a ValidationError mentionning the field's translated label
Basically, a deep clone, so that no reactive property will exist anymore.
This hook tells react when an instance of SchemaNode changes including
external factors such as the DeclarativeFormContext containing the sharedContext.
instance of SchemaNode to watch for changes
Generated using TypeDoc
Used to defines Props (or a function returning Props) for a function without the usual schema node props and it's children. That way we can only focus on the special Props without knowing about the library's internals