-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[Refactor] Split up RangeSelector.cs file #3822
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
[Refactor] Split up RangeSelector.cs file #3822
Conversation
Thanks RosarioPulella for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌 |
Microsoft.Toolkit.Uwp.UI.Controls.Input/RangeSelector/RangeSelector.Input.Drag.cs
Outdated
Show resolved
Hide resolved
Microsoft.Toolkit.Uwp.UI.Controls.Input/RangeSelector/RangeSelector.Properties.cs
Outdated
Show resolved
Hide resolved
This PR has been marked as "needs attention 👋" and awaiting a response from the team. |
into file based on type of input
These properties and their descriptions were confusing (and abbreviated) which made it difficult to understand how they differed from the Minimum/Maximum value properties. This clearly now separates which properties are being selected by the user. Their comments have been updated as well. It also aligns with the new Range struct field names in .NET: Start/End. original author: @michael-hawker
Microsoft.Toolkit.Uwp.UI.Controls.Input/RangeSelector/RangeSelector.Events.cs
Outdated
Show resolved
Hide resolved
This PR has been marked as "needs attention 👋" and awaiting a response from the team. |
Cool assuming we pass CI and the Sample works the same, I think we'll be good here! :) @Kyaa-dost want to take it for a spin too? It should behave the same as the existing control in the 6.1 app. Basically as long as the StepFrequency is small and within the bounds and a factor of the total range, I think it's fine. I've left the original bug I filed open for 7.1 and we can do more investigations later. |
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 to me 🚀
CI failing, its prob the stylecop stuff. Looking into it. |
Fixed CI |
Fixes #None
PR Type
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?
PR Checklist
Please check if your PR fulfills the following requirements:
Other information