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
Reach Schema should come with a sensible default behavior. However, ceratin use cases may want to modify how a schema is applied. Examples of such modifications may be:
Custom resolver function arguments
Custom actual data traversal method
Specification
import{createSchemaFunctor}from'reach-schema'constapplyCustomSchema=createSchemaFunctor({traverse: (tree,node)=>{},resolver: (value)=>{}})applyCustomSchema({data: ({ value })=>value!==2},{data: 'value'})
Call signatures to be designed
The text was updated successfully, but these errors were encountered:
Main motivation for this feature is to be able to create variable schemas that inherit the same behavior. The principle of the library remains the same, while certain aspects like traversal algorithm or a resolver signature vary.
Reach Schema should come with a sensible default behavior. However, ceratin use cases may want to modify how a schema is applied. Examples of such modifications may be:
Specification
The text was updated successfully, but these errors were encountered: