-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Remove OptionSet and Workspace from TypeScript and F# Inline Rename interfaces #58381
Conversation
382211b
to
8bd26b5
Compare
67b70e7
to
976ea90
Compare
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 get what this PR is doing, but I do wish the Obsolete messages generally pointed to their replacements, or at least to a tracking bug or something that when closed means all of that stuff could be deleted. Otherwise I imagine us leaving a bunch of this around or later being confused what the old stuff is for.
...ditorFeatures/Core/ExternalAccess/VSTypeScript/Api/IVSTypeScriptEditorInlineRenameService.cs
Show resolved
Hide resolved
src/EditorFeatures/Core/Implementation/InlineRename/InlineRenameService.cs
Outdated
Show resolved
Hide resolved
src/EditorFeatures/Core/Implementation/InlineRename/IEditorInlineRenameService.cs
Outdated
Show resolved
Hide resolved
src/Tools/ExternalAccess/FSharp/Editor/IFSharpEditorInlineRenameService.cs
Show resolved
Hide resolved
src/Tools/ExternalAccess/FSharp/Editor/InlineRename/FSharpInlineRenameLocation.cs
Show resolved
Hide resolved
I can file a bug: #58442. I don't think adding messages adds any value since I'm already updating TS and F# as well. |
@jasonmalinowski Any more feedback? |
I'd disagree, simply because we've had a bunch of times where we create a replacement, the consuming side updates, and we then forget to actually do the follow-up. I appreciate the tracking bug but unless it's listing what is actually obsolete it's a huge mess to sort out later if you're either not the original author, or it's been long enough you have to page it back into memory. |
...rFeatures/Core/ExternalAccess/VSTypeScript/Api/VSTypeScriptInlineRenameReplacementWrapper.cs
Show resolved
Hide resolved
The issue links to this PR. It's easy to look at the diff and remove the types that are marked Obsolete here. |
Replaces TS and F# external interfaces with equivalent abstract classes (with updated signatures) to allow easier modifications in future.
Minor fix in OmniSharpRenamer
F#:
dotnet/fsharp#12527
TypeScript:
https://devdiv.visualstudio.com/DevDiv/_git/TypeScript-VS/pullrequest/370211