Respect is_required
and is_disabled
in Field controls.
#405
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.
Control is an actual HTML form element or multiple elements that represent the "core" part of the Field.
Field template handles passing own props to controls if the controls do not already have them.
But for
is_required
andis_disabled
this does not happen. This leads to inability to create complex fields with multiple controls passed to the Field.This fixes the
Field
control element not respecting existingis_required
andis_disabled
that exist oncontrol
.