feat: add HelperText input primitive#646
Open
isaquebock wants to merge 16 commits into
Open
Conversation
Introduce `@aziontech/webkit/inputs/helper-text` — a small text element that renders auxiliary copy below a form field. The `kind` prop drives the visual tone: - `helper` (default): muted token, neutral copy. - `required`: warning-tone copy paired with the Required tag treatment. - `invalid`: danger-tone copy for validation errors; usually wired to `aria-describedby` on the input. - `disabled`: muted with a leading lock icon. The component is the helper line only — wrapping form-field components own the wiring of `aria-describedby` and the conditional rendering.
This was referenced Jun 17, 2026
HerbertJulio
previously approved these changes
Jun 22, 2026
pauloSF0
previously approved these changes
Jun 24, 2026
HerbertJulio
previously approved these changes
Jun 24, 2026
HerbertJulio
previously approved these changes
Jun 25, 2026
robsongajunior
requested changes
Jun 25, 2026
HerbertJulio
previously approved these changes
Jun 25, 2026
HerbertJulio
approved these changes
Jun 25, 2026
HerbertJulio
added a commit
that referenced
this pull request
Jun 25, 2026
… not undefined (#671) * [NO-ISSUE] chore(specs): default optional text props to empty string, not undefined Optional string props that hold renderable text now default to '' across the spec template, the spec-create / component-scaffold skills, and the scaffolder agent. Reserve undefined (unquoted) for props where absence differs from empty (open, modelValue, src); never the literal 'undefined'. Prevents the default-value issue raised in review of PR #646. * [NO-ISSUE] chore(specs): reject string-literal 'undefined' in spec Default cells Enforces the empty-string default convention documented earlier in this PR via spec-validate Step 3 plus a shared defaultCellIsStringUndefined helper and a unit test; status:implemented specs (checkbox/dropdown) are not re-validated so they stay green. --------- Co-authored-by: ROBSON.JUNIOR <robsongajunior@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
4 participants
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.
Summary
Introduce
@aziontech/webkit/inputs/helper-text— auxiliary text below a form field, with akindprop that drives the visual tone:helper(default) — muted, neutral copy.required— warning-tone copy paired with the Required tag treatment.invalid— danger-tone copy for validation errors; usually wired toaria-describedbyon the input.disabled— muted with a leading lock icon.The component is the helper line only — wrapping form-field components own the wiring of
aria-describedbyand the conditional rendering.Test plan
pnpm --filter @aziontech/webkit lint— clean.Webkit/Inputs/HelperText→ all fourkindvariants render with the expected tokens.