Create a XAML language service
It would be awesome to start working towards a proper XAML editor in VS Code. A few things off the top of my head that this would need to accomplish: 1. Provide intellisense when user is editing xaml files 2. Provide syntax highlighting 3. Not be tied to a particular XAML dialect, and be extensible so we can build UWP/WPF/Xamarin.Forms/Avalonia experiences inside VS Code on top of it. I'm not entirely familiar with how a VS code language service operates. I've only very briefly dabbled with them a few months ago, but I feel like the Omnisharp project is the right place for this to reside. /cc @kekekeks @michael-hawker @danwalmsley @grokys
Posted by stevenbrix on Oct 11, 2019, 12:32 AM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
Create a XAML language service
It would be awesome to start working towards a proper XAML editor in VS Code. A few things off the top of my head that this would need to accomplish: 1. Provide intellisense when user is editing xaml files 2. Provide syntax highlighting 3. Not be tied to a particular XAML dialect, and be extensible so we can build UWP/WPF/Xamarin.Forms/Avalonia experiences inside VS Code on top of it. I'm not entirely familiar with how a VS code language service operates. I've only very briefly dabbled with them a few months ago, but I feel like the Omnisharp project is the right place for this to reside. /cc @kekekeks @michael-hawker @danwalmsley @grokys
Comments (0)
No comments yet. Start the discussion.