Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Polishing Input, Area, Chip, Dropdown #8581

Merged
merged 7 commits into from
Nov 13, 2024
Merged

Polishing Input, Area, Chip, Dropdown #8581

merged 7 commits into from
Nov 13, 2024

Conversation

Duncid
Copy link
Contributor

@Duncid Duncid commented Nov 12, 2024

Description

Polishing Input, Area, Chip, Dropdown

Risks

UI breaks

@Duncid Duncid requested a review from JulesBelveze November 12, 2024 15:04
@Duncid Duncid changed the title WIP Polishing Input, Area, Chip Nov 12, 2024
@Duncid Duncid changed the title Polishing Input, Area, Chip Polishing Input, Area, Chip, Dropdown Nov 12, 2024
JulesBelveze and others added 5 commits November 12, 2024 16:43
 - Abstract animated text background and text color variants into separate records for cleaner code structure
 - Use cva utility from `class-variance-authority` to manage TextArea component styles, introducing a more flexible and scalable approach to variant handling

[sparkle] - fix: mark `isBusy` prop in `Chip` component as potentially undefined

 - Adjust typings for `isBusy` prop to correctly reflect its optional nature in the `Chip` component

[sparkle] - refactor: introduce cva to refactor `TextArea` styles and variants

 - Consolidate `TextArea` styling and variant handling into a single cva call to improve readability and maintainability
 - Simplify the props destructuring in the `TextArea` component by relying on cva to handle default variants and classes
…verable`

 - Introduced `cva` for more scalable handling of className variations based on component variants
 - Replaced manual className construction with `cva` utility in `Hoverable` component for maintainability and readability improvements
Copy link
Contributor

@JulesBelveze JulesBelveze left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I'll just publish a release candidate and deploy it to front edge to check we not breaking anything 👌🏼

@JulesBelveze JulesBelveze merged commit 7779c7d into main Nov 13, 2024
4 checks passed
@JulesBelveze JulesBelveze deleted the EdSparkle1211 branch November 13, 2024 08:07
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