Kevin Schneider

Note that we cannot get rid of the way we extend the `Chart` type (with nested [] attributes instead of `type Chart with`) because we cannot access the F# type...

On first look on that huge error stack that looks to me like an issue with PuppeteerSharp rather than Plotly.NET itself. Hard to know without seeing the code.

Weird, but let's take that as a win :D

Thanks for the heads-up. > this extension could be built without dependencies on .NET Interactive by using convention based formatting and .dib to load the extension It must stop being...

@jonsequitur That's what i was thinking, thanks. I'll look into it

@jonsequitur I finally had a first go at this, and I'd love some guidance on how to actually test this. I have implemented the (_I think_) equivalents of the no-dependency...

@jonsequitur I tried to isolate the issue more and ported that test, however it just tests if the formatted string is correct, which we already know that it is not....

@Thorium thanks - that feels more like a workaround though, since the client generated by the provider creates API calls that are wrong according to the schema. I have taken...

>Did it use to work before? Nope, this is the first message that i got from the kernel after following the install steps. I also tried to test it locally...

This is the first time i tried it (never have used it before), but i can try pinning previous versions, any recommendations on which version to try?