smolck

What's the thought on how to fix this? Special-case these options or . . . ?

@mhartington Are you familiar with how new APIs like this are generated with this library? I'd like to update this but can't seem to find how that's done.

Right, but are those written by hand and not generated (via reading the output from `$ nvim --api-info`)?

Okay, thank you! I think I might write something to generate them then . . .

Okay so I've added docs (rough draft) for the UI events; turns out the `ui.txt` docs for the ui events aren't easily available for use, and I'm not sure if...

Okay so some of the rest of the documentation-related warnings, specifically those for certain params not being documented, I'm not quite sure why the docs aren't being generated to fix...

Hmm I think part of my problem is the library is using/supports an outdated version (2.0.0) of .NET Core, and I'm using version 3.1(.3)?

This is something I'd really like to see for the UI events specifically, as every Rust GUI (including one I'm working on myself) has to implement the UI event deserialization...

> Hey, sounds very cool. I've made up my mind about serde, I'm open to add it as a dependency for sure now (I wasn't really on the fence, I...

> even then, maybe doing it in the new PR might be better Yeah my plan is to do a separate PR with the commits from that branch, and then...