Repository navigation
Replace HeroUI with owned components and migrate to Tailwind 4 - #1933
Merged
Merged
Conversation
Add a Pixels styling provider, owned semantic merge rules, and packed consumer type checks. Record the HeroUI migration inventory while preserving legacy cn behavior during coexistence.
Package light and dark tokens with Tailwind utilities and verify CSS exports and built-source discovery in a plugin-free tarball consumer.
Add explicit label, description, and error IDs without changing RHF validation timing. Cover custom controls and packaged inference, and capture light/dark field baselines.
Treat nullish display values as empty and use the supported NaN sentinel for the legacy number renderer. Add a null/zero/clear regression story without changing empty-field submission normalization.
Preserve autosizing, controlled values, focus refs, slot types and RHF/Veto timing with React Aria and the existing autosizing engine. Move label spacing onto both owned text-field labels to retain the original control-to-error spacing.
BREAKING CHANGE: Remove uniform/hooks/useInput, uniform/hooks/useUniformField, and uniform/hooks/useUniformFieldArray with their public helper types and presentation getters. Custom controls must use useController/useFormContext and own their presentation. RadioBox no longer inherits HeroUI-only props.
- introduce shared field layout, label and description partials - clarify Input subcomponent ownership and centralize clear behavior - reorganize radio controls and segmented field styling - expand styling slots and consolidate validation message rendering - update consumers, tests, stories and migration documentation - add component READMEs and code style guidelines
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Harden snapshot autofix and improve sensitive data redaction
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
 |
Contributor
Author
|
@coderabbitai help |
ChatThere are 3 ways to chat with CodeRabbit:
CodeRabbit commands
Other keywords and placeholders
Status, support, documentation and community
|
Contributor
Author
|
@coderabbitai full review |
|
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.
Summary
Removes HeroUI across Pixels, Uniform and their consumers. Components now use owned styling and React Aria where appropriate, with shared field layouts and smaller control subcomponents.
Moves Tailwind configuration to CSS-first Tailwind 4, including owned semantic tokens, explicit source discovery and consumer styling support.
Breaking changes
herouiexport@fuf-stack/pixel-utils/tokens.css, configure package source scanning and replace--heroui-*overrides with--pixel-*useInputusage before upgradingMigration instructions are in
docs/uniform/migration.mdanddocs/styling.md.Validation
Follow-up
Previously documented color-contrast issues remain separate theme work.