Skip to content
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 legacy completion #38569

Merged
merged 18 commits into from
Sep 19, 2019
Merged

Remove legacy completion #38569

merged 18 commits into from
Sep 19, 2019

Conversation

ivanbasov
Copy link
Contributor

No description provided.

@ivanbasov ivanbasov added Area-IDE IDE-IntelliSense Completion, Signature Help, Quick Info labels Sep 7, 2019
@ivanbasov ivanbasov added this to the 16.4 milestone Sep 7, 2019
@ivanbasov ivanbasov requested review from a team as code owners September 7, 2019 00:36
@CyrusNajmabadi
Copy link
Member

CyrusNajmabadi commented Sep 7, 2019

have not actually reviewed this. I presume it's just almost entirely the removal of the old code. so instead of looking at all that, was there anything more 'interesting' than that? if so, can you comment any areas that need particular attention? #Resolved

@jinujoseph
Copy link
Contributor

jinujoseph commented Sep 8, 2019

cc @KirillOsenkov for info and review
cc @sandyarmstrong #Resolved

@jasonmalinowski
Copy link
Member

jasonmalinowski commented Sep 9, 2019

@ivanbasov Can we target this at master? I recognize it'll create some merge conflicts into master-vs-deps, but does that make the code easier to maintain in master in the mean time? #Resolved

@ivanbasov
Copy link
Contributor Author

ivanbasov commented Sep 9, 2019

@ivanbasov Can we target this at master? I recognize it'll create some merge conflicts into master-vs-deps, but does that make the code easier to maintain in master in the mean time?

Thank you, @jasonmalinowski ! Good idea! Let us meet merge conflict once, rather than supporting 2 branches for a longer time. Will rebase into master. #Resolved

@ivanbasov
Copy link
Contributor Author

ivanbasov commented Sep 9, 2019

have not actually reviewed this. I presume it's just almost entirely the removal of the old code. so instead of looking at all that, was there anything more 'interesting' than that? if so, can you comment any areas that need particular attention?

Thank you, @CyrusNajmabadi ! I hope it is just a technical change: remove tests and remove the old implementation. I am not going to add anything interesting here. #Resolved

@ivanbasov ivanbasov changed the title Remove legacy completion WIP: Remove legacy completion Sep 9, 2019
@ivanbasov ivanbasov changed the base branch from master-vs-deps to master September 9, 2019 18:31
Copy link
Member

@jasonmalinowski jasonmalinowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Primary concern is there are some tests that didn't get switched back to Facts, and thus they won't run. I know @sharwell was discussing a bit getting some of the xunit analyzers running on VB as well....this might be a really good reason to do so since it'd be hugely easy to make more mistakes like that.

src/VisualStudio/Core/Test/Snippets/SnippetTestState.vb Outdated Show resolved Hide resolved
src/VisualStudio/Core/Test/Snippets/SnippetTestState.vb Outdated Show resolved Hide resolved
src/VisualStudio/Core/Test/Snippets/SnippetTestState.vb Outdated Show resolved Hide resolved
src/VisualStudio/Core/Test/Snippets/SnippetTestState.vb Outdated Show resolved Hide resolved
ivanbasov and others added 3 commits September 9, 2019 17:40
Co-Authored-By: Jason Malinowski <jason@jason-m.com>
Co-Authored-By: Jason Malinowski <jason@jason-m.com>
Co-Authored-By: Jason Malinowski <jason@jason-m.com>
@sharwell

This comment has been minimized.

@jasonmalinowski

This comment has been minimized.

@sharwell

This comment has been minimized.

@ivanbasov
Copy link
Contributor Author

ivanbasov commented Sep 13, 2019

Feedback addressed. @jasonmalinowski and @sharwell please review/unblock #Resolved

@jasonmalinowski jasonmalinowski dismissed their stale review September 13, 2019 21:38

Unblocking review as I won't have time to re-review.

@ivanbasov ivanbasov changed the title WIP: Remove legacy completion Remove legacy completion Sep 13, 2019
@@ -304,12 +304,6 @@ private void StartRemoteIntegrationService(DTE dte)
{
dte.ExecuteCommand(WellKnownCommandNames.Test_IntegrationTestService_Start);
}

if (AsyncCompletionCondition.Instance.ShouldSkip
&& dte.Commands.Item(WellKnownCommandNames.Test_IntegrationTestService_DisableAsyncCompletion).IsAvailable)
Copy link
Member

@sharwell sharwell Sep 16, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❕ This command needs to be removed from WellKnownCommandNames and from the VSCT. #Resolved

Copy link
Member

@sharwell sharwell Sep 18, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 This is still problematic. Here are the locations I know need to be updated. There may be additional references that become obvious when you try to remove them.

<IDSymbol name="cmdidDisableAsyncCompletion" value="0x5203" />

<Button guid="guidTestWindowCmdSet" id="cmdidDisableAsyncCompletion" priority="0x0030" type="Button">
<Parent guid="guidTestWindowCmdSet" id="grpidIntegrationTestService" />
<Strings>
<ButtonText>Disable Async Completion</ButtonText>
<CommandName>IntegrationTestService.DisableAsyncCompletion</CommandName>
<CanonicalName>IntegrationTestService.DisableAsyncCompletion</CanonicalName>
<LocCanonicalName>IntegrationTestService.DisableAsyncCompletion</LocCanonicalName>
</Strings>
</Button>

public const int cmdidDisableAsyncCompletion = 0x5203;

var disableAsyncCompletionMenuCmdId = new CommandID(guidTestWindowCmdSet, cmdidDisableAsyncCompletion);
_disableAsyncCompletionMenuCmd = new MenuCommand(DisableAsyncCompletionCallback, disableAsyncCompletionMenuCmdId)
{
Enabled = true,
Visible = false,
};
menuCommandService.AddCommand(_disableAsyncCompletionMenuCmd);

private readonly MenuCommand _disableAsyncCompletionMenuCmd;

private void DisableAsyncCompletionCallback(object sender, EventArgs e)
{
if (!_disableAsyncCompletionMenuCmd.Enabled)
{
return;
}
var componentModel = ServiceProvider.GetService<SComponentModel, IComponentModel>();
var featureServiceFactory = componentModel.GetService<IFeatureServiceFactory>();
featureServiceFactory.GlobalFeatureService.Disable(PredefinedEditorFeatureNames.AsyncCompletion, EmptyFeatureController.Instance);
_disableAsyncCompletionMenuCmd.Enabled = false;
}
#Resolved

@ivanbasov ivanbasov merged commit cf78aee into dotnet:master Sep 19, 2019
@ivanbasov ivanbasov deleted the removelegacy branch September 19, 2019 04:31
NTaylorMullen added a commit to dotnet/razor that referenced this pull request Nov 5, 2019
- It's no longer possible to turn off async completion
- Roslyn has already removed their legacy completion support: dotnet/roslyn#38569
- VS4Mac supports async completion.
- This is required to target newer versions of Roslyn because they changed their legacy completion types.
NTaylorMullen added a commit to dotnet/razor that referenced this pull request Nov 14, 2019
- It's no longer possible to turn off async completion
- Roslyn has already removed their legacy completion support: dotnet/roslyn#38569
- VS4Mac supports async completion.
- This is required to target newer versions of Roslyn because they changed their legacy completion types.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE IDE-IntelliSense Completion, Signature Help, Quick Info
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants