-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Move sub-classes of "UpDownBase", "WebBrowser" and "WebBrowserBase" classes to their own files #4579
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
Move sub-classes of "UpDownBase", "WebBrowser" and "WebBrowserBase" classes to their own files #4579
Conversation
2ec2db0
to
d453abc
Compare
Codecov Report
@@ Coverage Diff @@
## main #4579 +/- ##
===================================================
+ Coverage 97.96538% 97.96539% +0.00001%
===================================================
Files 540 540
Lines 263145 263146 +1
Branches 4923 4923
===================================================
+ Hits 257791 257792 +1
Misses 4478 4478
Partials 876 876
Flags with carried forward coverage won't be shown. Click here to find out more. |
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.
👍
...ms/UpDownBase.UpDownButtons.UpDownButtonsAccessibleObject.DirectionButtonAccessibleObject.cs
Outdated
Show resolved
Hide resolved
...ows.Forms/src/System/Windows/Forms/UpDownBase.UpDownButtons.UpDownButtonsAccessibleObject.cs
Outdated
Show resolved
Hide resolved
src/System.Windows.Forms/src/System/Windows/Forms/WebBrowser.WebBrowserSite.cs
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.
I know this is mostly moving around the code but its better to clean the parts of the code we are touching. Added some nits and suggestions we are following in the designer repo.
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.
are these missing naming convention?
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.
nit: we are encouraging condition expressions in other repos we own. Lets do that in this repo as well, at least in the code we are refactoring.
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.
We did few passes over parts of the codebase in the past, we should do another sweep. This is separate piece of work though.
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.
I understand that. But that separate work will keep postponed or never make to priority list. In the designer repo, we make it norm that if we touch the code, we clean it as much as possible. In this case, i do not see cleaning would be risky or time taking. Happy to chat offline.
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.
nit: conditional expression? and in other places in 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.
targetFrameName can not be empty here?
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.
should we throw if parent is null?
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.
This falls into the NRTA initiative. Personally I'm inclined to do it separately for ease of tracking, and to avoid slowing down cleanups like this one.
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.
seems private class, is this hiding base class method?
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.
lets not abbreviate declarations. In other repos, we are enforcing to give meaningful/readable names.
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.
nit: expressional bodies here and below.
…lasses to their own files
d453abc
to
55ccd11
Compare
Hi @dreddy-work. In this PR we are simply moving the sub-classes into separate files to keep the changes as simple and safe as possible. I suggest creating a separate ticket for refactoring. |
I understand that. Approach we follow in designer repo is, if we are touching the code base, we clean it up. in this case, it shouldn't be hard. I see this is going into main. So, risk is less. |
Proposed changes
Customer Impact
Regression?
Risk
Test environment(s)
Microsoft Reviewers: Open in CodeFlow