Question: How to rewrite maui without breaking VS editor?

[wjk]

As stated in #28 (comment), I have some ideas on how to improve or extend Maui that may involve a partial or full rewrite of the guts of the platform. Honestly, if I am going to start such a rewrite, I would greatly prefer to start over from scratch with Maui instead of having to adapt the current codebase. (As I understand it, many of the problems currently extant in Maui are due to historical design issues and/or bugs from Xamarin.Forms's past.)

However, if I do this, I will almost certainly break XAML editor support because it is coded to work with Xamarin.Forms's XAML implementation only. Because Maui currently uses the same ProjectCapability as upstream Xamarin.Forms, I can simply copy that capability into my rewrite branch. Furthermore, since the editor code is proprietary, I do not know what other elements of Maui as it exists today are required to stay as-is to avoid breaking the editor.

Note that the scope of this issue explicitly does not include the graphical designer, mostly because I rarely (if ever) use it. I am concerned with the XAML editor support (IntelliSense and smart syntax coloring) only. I would like to keep compatibility with both VSMac and VSWindows, however. Thanks!