Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in #716, new lifecycle APIs made efficient automatic bridge creation harder (impossible without additional API). This change removes
createSchemaBridge
completely, meaning that:bridge
inBaseForm
state.check
onBridge
and subclasses.schema
prop ofBaseForm
have to manually create bridge instance.My motivation is not only the performance gain (strict equality check instead of almost no-op
createSchemaBridge
checks) and removal of a state property (which was always a copy ofprops.schema
for GraphQL and JSON schemas) but also simplification of the public API - the transformation of a schema to a bridge is now explicit.