-
Notifications
You must be signed in to change notification settings - Fork 14
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
[FX-4601] Migrate Slider to TailwindCSS #4272
Conversation
🦋 Changeset detectedLatest commit: 2677289 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few comments, but overral nice work!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work! Left some comments
88d5875
to
1b60b0e
Compare
1306bbc
to
a9b1c47
Compare
9ee3cff
to
18a9600
Compare
9ed21ad
to
7c9a7d9
Compare
@toptal-anvil ping reviewers |
@toptal-anvil ping reviewers |
isOverlaped, | ||
isFirstLabel, | ||
currentPlacement, | ||
}: GetPositionProps) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since, it's a separate function, I would also define a return type.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
* Add the Slider from MUIBase * Refactor components to accommodate migration * Adapt stories and remove unused files * Fix a small existing bug on Tooltip Story * Update snapshots * Add changeset * Update rail slot to fix Happo Story failed test * Update snapshots after changes on rail slot * Address part of review comments * Revert back ValueLabel to a span * Test commit * Update yarn * Revert "Revert back ValueLabel to a span" * Change ValueLabel to a span after revert * Update snapshots * Refactor ValueLabel * Move slots components outside the Slider * Add unit tests for getPosition util function * Refactor SliderValueLabel * Refactor hook * Refactor hook and util function * Add unit tests for hooks * Add changeset file * Update changeset * Change position of Label when out of screen * Fix doc generation * Update yarn.lock * Remove logs * Fix spacing * Update snapshots * Update snapshots * Address comments * Rename property to cleaner code * Fix tests * Refactor ValueLabel * Fix tests * Refactor logic to hook * Address comments * Address comments --------- Co-authored-by: TomasSlama <tomas.slama@toptal.com>
FX-4601
Description
This PR changes the Slider component to use the Slider from the MUI Base UI and applies styles using TailwindCSS.
Notes:
compact
andTooltipComponent
props have been removed due to unnecessary extra work that doesn't match the designs. This was agreed between Tomas and Matt Vela.How to test
Screenshots
Development checks
Read CONTRIBUTING.md and Component API principlesAnnotate allprops
in component with documentationCreateexamples
for componentEnsure that deployed demo has expected results and good examplesEnsure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.Covered with tests (visual tests included)Breaking change
codemod is created and showcased in the changesettest alpha package of Picasso in StaffPortalPR commands
List of available commands:
@toptal-bot run package:alpha-release
- Release alpha version@toptal-anvil ping reviewers
- Ping FX team for reviewPR Review Guidelines
When to approve? ✅
You are OK with merging this PR and
nit:
to your comment. (ex.nit: I'd rename this variable from makeCircle to getCircle
)When to request changes? ❌
You are not OK with merging this PR because
When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:
How to handle the comments?