Roland Fredenhagen

Makes sense, I thought I could skip the CLI and have some more Type safety etc. at the boundary. But I'll just depend on `cargo-edit` being installed, and as soon...

> "IDE-like experience for `Cargo.toml`" which made me want a `cargo-analyzer`. I mean, something like `unresolved crate, add "..."="0.1.0" to your Cargo.toml` via a quick fix by would be something...

Right, there is something similar, but not a general LSP only nvim specific: https://github.com/Saecki/crates.nvim But having that as a companion to `rust-analyzer` as a dependency manager would be quite nice,...

Yeah, just a general Idea, as a lot of people use cargo edit to manage their dependencies, and running `cargo add` does not reload rust-analyzer.

I had a bit more thinking about the whole thing. On the naming, fields are also breaking changes to refactor IIRC so I wouldn't see it too problematic to use...

Secondly on the whole migration thing, other than liquibases approach with external scripts, I would propose something in code. Something like ```rs #[derive(Collection)] // Original definition (implicitly v=0) #[collection(name="hello", authority="test")]...

One immediate flaw I see in my definition, is... what is the current status. For the `struct` it appears to be `v=2` but for the fields it is an unspecified...

Makes sense, didn't think about the serde features, but an actual versioned system at some point would make sense. And people are probably already used to needing to add such...

Maybe when introducing time, timezone conversion could also be something great to have

> Since I like this PR, I worked on it. I changed the notification system to switch mX led if `g910-leds` is available (instead of colorizing the logo). > >...