-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Add range slider support for 7.0 #17913
Conversation
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.
It looks like this change to the 7.0
branch may not have been submitted to master
yet. Now that version 8 has released, all changes must be submitted to the master
branch first (except in emergencies or if the change is irrelevant to version 8).
Please do one of the following:
- If you've already created a PR to
master
, add a link to it - If the change is irrelevant to version 8, add a comment explaining why
- Otherwise, create a PR to
master
with this same change, and add a link to it
After that, you can dismiss this review and remove the "needs cherry-pick" label (or ask a team member to help do so).
Want to avoid this in the future? Include text like "Cherry-pick of ####" in the PR description (where #### is the real master
PR number).
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit cf7d19e:
|
Asset size changes
Over Tolerance (1024 B) Over Baseline Below Baseline New Removed 1 kB = 1000 B Baseline commit: ac2f319d76db747f0d0b1d76cbf4d63ae8864794 (build) |
Perf AnalysisNo significant results to display. All results
|
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.
Looks good, but we want to be sure that existing, non-ranged
sliders render the same as they did before this change. I added a few comments in places that appear different, but there are probably other places that need a ranged
check. There shouldn't be changes to test snapshots for unrelated components.
...ages/react-examples/src/office-ui-fabric-react/__snapshots__/Facepile.Basic.Example.tsx.shot
Outdated
Show resolved
Hide resolved
packages/office-ui-fabric-react/src/components/Slider/Slider.base.tsx
Outdated
Show resolved
Hide resolved
packages/office-ui-fabric-react/src/components/Slider/Slider.base.tsx
Outdated
Show resolved
Hide resolved
…ase.tsx Co-authored-by: Ben Howell <48106640+behowell@users.noreply.github.com>
packages/office-ui-fabric-react/src/components/Slider/Slider.styles.ts
Outdated
Show resolved
Hide resolved
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.
Looks good! Thanks for making the changes to clean up the snapshots.
Thanks for approval! Do you know how would we merge it though since it doesn't pass the size auditor check? |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
🎉 Handy links: |
Pull request checklist
$ yarn change
Description of changes
Add range slider support for 7.0. The work for v8 is already done here: #16854.
There has been asks inside Azure teams that we need this feature in V7, so this PR fulfills that.