-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Precursor work to merge EditorFeatures.WPF into EditorFeatures. #78308
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
base: main
Are you sure you want to change the base?
Conversation
internal sealed class EditorPeekableItemFactory( | ||
IMetadataAsSourceFileService metadataAsSourceFileService, | ||
IGlobalOptionService globalOptions, | ||
IThreadingContext threadingContext) : PeekableItemFactory(metadataAsSourceFileService, globalOptions, threadingContext); |
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.
core code merged down (as is still exported for us to use. This is just a remnant so xaml can still import this until we move them to use the coe in the ea layer.
src/EditorFeatures/Core/Microsoft.CodeAnalysis.EditorFeatures.csproj
Outdated
Show resolved
Hide resolved
|
||
namespace Microsoft.VisualStudio.LanguageServices.Xaml.Features.Peek; | ||
|
||
internal interface IXamlPeekableItemFactory |
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.
new EA layer code for xaml to use.
@jasonmalinowski ptal. |
This moves everything down, except for special code we expose to Xaml to allow them to use our Peek service. This PR also adds code into their existing EA layer to do this instead.
So we can:
Precursor to #77707