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

Disable document outline #65688

Conversation

jmarolf
Copy link
Contributor

@jmarolf jmarolf commented Nov 30, 2022

workaround while we improve performance in #65641

CC: @allisonchou this a fix we want to get into the next servicing release.

@jmarolf jmarolf requested a review from a team as a code owner November 30, 2022 22:39
@CyrusNajmabadi
Copy link
Member

This feels weird to me. Say someone was using the feature. So they have the outlining window open. Now VS will launch and this will just be empty. Won't they think something is broken here? How would they know they need to enable this feature to get things working again?

@jmarolf
Copy link
Contributor Author

jmarolf commented Dec 1, 2022

This feels weird to me. Say someone was using the feature. So they have the outlining window open. Now VS will launch and this will just be empty. Won't they think something is broken here? How would they know they need to enable this feature to get things working again?

#65641 is expected to be the final resolution to this. this is a stop gap to unblock users who have the document outline window opened for other reasons (such as XAML) and who currently have no other recourse.

@CyrusNajmabadi
Copy link
Member

I guess my point is: can we make this less confusing for users who run into this? For example, we could put a message (or button) in the ui explaining that this is not working for C#/VB until the option is explicitly enabled.

@jmarolf
Copy link
Contributor Author

jmarolf commented Dec 1, 2022

I guess my point is: can we make this less confusing for users who run into this? For example, we could put a message (or button) in the ui explaining that this is not working for C#/VB until the option is explicitly enabled.

Not a bad idea, I'll ask what the rules are for getting a new translation in for that text. Question would be what we do if the translation team couldn't turn it around in time for the servicing release. Would we want to wait for the next servicing release? I don't think we are allowed to release un-translated strings in a servicing patch.

@jmarolf
Copy link
Contributor Author

jmarolf commented Dec 1, 2022

@dotnet/roslyn-infrastructure it appears that integration tests in the release/17.4 branch are failing consistently I assume those failures should not block merge.

@jmarolf
Copy link
Contributor Author

jmarolf commented Dec 1, 2022

I guess my point is: can we make this less confusing for users who run into this? For example, we could put a message (or button) in the ui explaining that this is not working for C#/VB until the option is explicitly enabled.

At this point we can't add new strings in a servicing update. I am open to options here but I think if we want to insert this now we should do so as is.

@jmarolf
Copy link
Contributor Author

jmarolf commented Dec 1, 2022

missed window for this to be relevant

@jmarolf jmarolf closed this Dec 1, 2022
@jmarolf jmarolf reopened this Dec 7, 2022
@jmarolf
Copy link
Contributor Author

jmarolf commented Dec 8, 2022

@arkalyanms I believe integration tests are broken in the release/dev17.4 branch so I assume this is good to go once its reviewed

@jmarolf
Copy link
Contributor Author

jmarolf commented Dec 8, 2022

@jasonmalinowski We've decided we'd like to take this change for servicing. Can you review?

private const string FeatureName = "DocumentOutlineOptions";

public static readonly Option2<bool> EnableDocumentOutline = new(FeatureName, nameof(EnableDocumentOutline), defaultValue: false,
storageLocation: new FeatureFlagStorageLocation("Roslyn.DocumentOutline"));
Copy link
Member

Choose a reason for hiding this comment

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

so we're disabling the feature entirely? there's no UI to get it back?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

that is correct

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.

😢

@jmarolf jmarolf changed the title Add option to enable/disable document outline and disable by default Disable document outline Dec 8, 2022
@jasonmalinowski jasonmalinowski merged commit 8131a70 into dotnet:release/dev17.4 Dec 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants