-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Razor EA changes to allow better tests in Razor #74402
Conversation
davidwengier
commented
Jul 16, 2024
- Moves things used for testing into a Testing folder so we know its safe to change
- Allows creation of the test language server with a different language server kind (for cohosting)
- Allows tests to use the RazorPinnedSolutionInfoWrapper
- Tiny bit of clean up
Also moved files needed for testing into a testing folder so we don't get them mixed up
[Shared] | ||
internal class RazorLanguageServerFactoryWrapper : AbstractRazorLanguageServerFactoryWrapper | ||
[Export(typeof(RazorTestLanguageServerFactory))] | ||
[Export(typeof(AbstractRazorLanguageServerFactoryWrapper))] |
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 abstract class is only used for this export, and was probably just copied from Razor where we used to use abstract classes a lot. I'm exporting it as itself now, so that we can remove the abstract class in future, but we have to wait until these changes make it to VS Preview images for that to happen, or the Roslyn integration tests will fail.
Part of #9519 and #10603 Requires dotnet/roslyn#74402 Removes a little more dodginess in the cohosting tests by actually using the `RazorPinnedSolutionInfoWrapper` for solution checksums, just like the real OOP services.