Kevin Schneider

@HLWeil @LibraChris any suggestions on the graph types you'd like to see in such an API?

> Normal you build a graph and try different layouts While i get this, i do not see it as an argument against the need for a top-level API. The...

Furthermore, if I would want to build a tree with this library at the moment, there would be quite some ceremony involved, although i know exeactly what kind of layout...

Here are some additional points after some F2F discussion with @muehlhaus and @LibraChris: - We should **not** name the top-level API `Graph` because - in contrast to `Chart` - it...

cc @HLWeil @omaus @Freymaurer

this should contain everything you need, including pageination handling etc. https://github.com/CSBiology/BIO-CSB-10-L-3/blob/main/material/II_LLMBasedLiteratureCuration/notebooks/1_RetrievingScientificKnowledge/1_RetrievingScientificKnowledge.ipynb @Freymaurer

@Freymaurer am am still assigned to this, but i think this is not in my scope of work at the moment, so i'll assign you muhahah

> When watching the docs `dotnet fsdocs watch --eval` I noticed the API-Reference is broken. Nothing is displayed. I'm not sure if the cause lies within this PR or some...

For reference, this is why we introduced [`Optional` for the native C# layer in `Plotly.NET.CSharp`](https://github.com/plotly/Plotly.NET/blob/dev/src/Plotly.NET.CSharp/Optional.cs) Using that type for optional values in the C# API makes C# API only slightly...

IIRC the problems start with generics and type constraints. E.g. If you try an arg with `seq` on the F# side and an equal type constraint in the C# wrapper...