-
Notifications
You must be signed in to change notification settings - Fork 196
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
Fix code actions (and code actions integration tests) #11141
Conversation
We were running most of them twice. Very confusing when you expect one test failure, but get two.
|
||
namespace Microsoft.AspNetCore.Razor.LanguageServer.CodeActions; | ||
|
||
public abstract class CodeActionEndToEndTestBase(ITestOutputHelper testOutput) : SingleServerDelegatingEndpointTestBase(testOutput) |
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.
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 did mention that we weren't consistent, and one of the ways we're not is that in product code we mostly use AbstractXXX
and in tests we use XXXBase
. I have no idea how we came to this state, and I am not trying to pick a side, but this naming convention seemed to fit best with where the change is.
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.
Fixes #10742 Needs dotnet/roslyn#75711 before it will build Also will need to merge in main once #11141 is merged
My bad. In #11135 I failed to notice that the
GenerateRazorCodeActionContextAsync
also modified the original code actions request, to handle an oddity of VS LSP, where it sends the users selected range (or cursor position) as a different property, and uses theRange
property as the whole line.