standarizing input sizes and paddings #579
Open
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.
feat: Implement two-size system for form controls and buttons
Add standardized sizing system with large (40px) and small (32px) variants for all interactive form controls and buttons to ensure consistent heights and perfect visual alignment across the design system.
Changes
New Features
sizeprop to all interactive components (default: 'large')Components Updated
Infrastructure
src/system/types/controlSize.tswith shared types and utilitiessizes.control.small/large)data-sizeattributeDocumentation
ControlSizes.stories.tsxwith comprehensive alignment examples and anti-pattern guidanceBreaking Changes
Height Changes:
Migration:
Use
size="small"prop on any component where the new 40px default causes layout issues.Technical Details
Size Calculations
All heights account for 1px borders on top and bottom:
Padding Strategy
Fixed-Size Components
Radio, Checkbox, and Toggle remain at standard sizes (16px, 14px, 40x20px) as these are established UI patterns that should not vary.
Testing
✅ TypeScript compilation: 0 errors
✅ ESLint linting: 0 errors
✅ Storybook visual verification: All components render correctly
✅ Accessibility: 0 violations in all size variant stories
✅ Alignment verified: Button + Input combinations align perfectly
Description
A few sentences describing the overall goals of the pull request. Any special considerations and decisions.
Also include any references to relevant discussions and documentation.
Checklist
Steps to Test
Outline the steps to test and verify the PR here.
Example:
npm run dev.