Siegfried Pammer
b729995435
Strip the WPF ILSpy/, ILSpy.Tests/, and ILSpy.BamlDecompiler/ projects and their solution entries so this commit can serve as the base for replaying the rewritten Avalonia history on top. The BAML plugin needed UseWpf + AvalonEdit and had a ProjectReference to ILSpy/ILSpy.csproj; once both are gone it cannot build and would block bisect for every intermediate commit. The Avalonia main app will absorb its three exports (factory, file handler, entry node) in the later "BAML to XAML decompiler integration" commit.
How does it work?
To extract the type info from the source assembly, ILSpy side-loads it including all its dependencies.
The extracted type info is structured into a model optimized for the HTML diagrammer and serialized to JSON. The model is a mix between drop-in type definitions in mermaid class diagram syntax and destructured metadata about relations, inheritance and documentation comments.
The JSON type info is injected into the
template.htmlalongside other resources like thescript.jsat corresponding{{placeholders}}. It comes baked into the HTML diagrammer to enable
- accessing the data and
- importing the mermaid module from a CDN
locally without running a web server while also avoiding CORS restrictions.
In the final step, the HTML diagrammer app re-assembles the type info based on the in-app type selection and rendering options to generate mermaid class diagrams with the types, their relations and as much inheritance detail as you need.