This bug isn't really specific to XamlDirective but it's the class where I found the issue and it's the easiest to cause an issue. You can have the bug when using instances of XamlMember or of any of ...
Executing the new planner results in the error below. This happens in my application using the nuget packages, but I get the same result using Example66 ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results