Skip to content

feat: Make borderWidthFieldStatusInlineStart design token public + themeable - #5196

Merged
SpyZzey merged 2 commits into
mainfrom
feat/design-token-input-error-warning-border-inline-start-public
Oct 27, 2026
Merged

SpyZzey merged 2 commits into
mainfrom
feat/design-token-input-error-warning-border-inline-start-public

Conversation

@SpyZzey

@SpyZzey SpyZzey commented Oct 27, 2026 •

Copy link
Copy Markdown
Member

Description

We want to make the inline-start border width for invalid and warning states themeable. Currently, this is only possible in the input component using the style api.

Proposal: Rename borderInvalidWidth (currently not themeable nor public) to borderWidthFieldStatusInlineStart. This matches our existing conventions in other tokens:

  • borderWidth prefix for all border-width tokens,
  • Field matches borderWidthField,
  • Status matches our existing status tokens, e.g., colorBorderStatusWarning,
  • InlineStart matches our existing directional tokens, e.g., borderWidthAlertInlineStart
Screenshot 2026-10-27 at 13 31 20

Related links, issue #, if available: n/a

How has this been tested?

Review checklist

The following items are to be evaluated by the author(s) and the reviewer(s).

Correctness

  • Changes include appropriate documentation updates.
  • Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
  • Changes do not include unsupported browser features, see CONTRIBUTING.md.
  • Changes were manually tested for accessibility, see accessibility guidelines.

Security

Testing

  • Changes are covered with new/existing unit tests?
  • Changes are covered with new/existing integration tests?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@SpyZzey SpyZzey changed the title feat: Make borderWidthFieldInvalidInlineStart design token public + themeable feat: Make borderWidthFieldStatusInlineStart design token public + themeable Oct 27, 2026
@SpyZzey
SpyZzey requested review from a team and georgylobko and removed request for a team and taheramr October 27, 2026 12:39
@SpyZzey
SpyZzey enabled auto-merge October 27, 2026 12:47
@codecov

codecov Bot commented Oct 27, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.73%. Comparing base (6997ceb) to head (c4e293e).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5196   +/-   ##
=======================================
  Coverage   97.73%   97.73%           
=======================================
  Files         998      998           
  Lines       32247    32247           
  Branches    11918    11918           
=======================================
  Hits        31517    31517           
  Misses        685      685           
  Partials       45       45           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@SpyZzey
SpyZzey added this pull request to the merge queue Oct 27, 2026
Merged via the queue into main with commit b7014ed Oct 27, 2026
71 checks passed
@SpyZzey
SpyZzey deleted the feat/design-token-input-error-warning-border-inline-start-public branch October 27, 2026 13:24

This branch was successfully deployed

3 active deployments
dev-pages-react18 — c4e293eb Deployed Oct 27, 2026 by SpyZzey via deploy (React 18) / deploy #2996
dev-pages-react16 — c4e293eb Deployed Oct 27, 2026 by SpyZzey via deploy (React 16) / deploy #2996
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants