-
Notifications
You must be signed in to change notification settings - Fork 772
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
Cleanup vs ext 2 #358
Closed
Closed
Cleanup vs ext 2 #358
Changes from 5 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
b60832b
remove #region
enricosada d6aa610
remove include external doc in comments
enricosada d222cd8
removed redundant comments
enricosada 05ea5ad
remove commented code
enricosada 074dae1
remove empty file
enricosada 999b3a3
removed comment
enricosada File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back 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.
I have sent a question to our MSDN doc team about whether this will break, internal doc generation tooling. My suspicion is that these comments are necessary. But I honestly don't know.
*** Update ****
Got the word back from the msdn doc guys, they don't recognize any of the files, so they believe it's safe to make these changes.
In some ways that's the problem with all of this clean up, it is certainly needed but there are more teams that depend on, and can make changes to this codebase than just us. That's not to say it isn't worth finding out, however, inadvertently breaking or even worse silently braking a bunch of teams who don't expect there to be any changes is always unfortunate.
I realize this seems silly, but I worry about these cleanup type PR's much more than the bug fix ones. It is true I may have been at Microsoft too long ... because often the principle of least change is the one that guides our 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.
i splitted changes in multiple commits 😄 , feel free to use what you think is ok.
I understand the uex include is good for reference doc/examples etc, so np if used, but i dont see this repo on msdn
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.
The F# language service definitely isn't documented on MSDN, but it doesn't hurt to double check with the doc people.
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.
sure, as i said, easy to remove this commit from pr.
With pr is easier to revert than ask and wait for permission
Btw maybe if these file are needed, the files exists in an internal repo of doc team? Doc is a good candidate for open source contribution.
just curious of msdn page source like List.append with example etc 😄
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.
@KevinRansom nice, thx