Repository navigation
Clarify Fieldset warnings and form wrapper property targets - #52
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add documentation-only guardrails to the form component APIs.
Document on
Fieldset::create()that group warning rendering does not wirearia-invalidoraria-describedbyonto arbitrary member controls; those associations remain the caller's responsibility. Document each component'swrapperProps()target: the outer div for text, email, password, and textarea controls; the fieldset for Fieldset; and a div or fieldset according to Select mode.No runtime behavior changes.
git --no-pager diff --checkpassed. Tests were not run because only docblocks changed.List of issues fixed
Fixes #44