NyxCode

Maybe this (removing all attributes except built-ins) is something syn's `Generics::split_for_impl` should do?

Hey! I have not yet found a nice way to reliably generate code for it, so I have not. If what you end up with looks general enough to be...

As far as I can tell, the only nice way of doing batch inserts is on Postgres, by binding arrays and using `UNNEST` ([docs](https://github.com/launchbadge/sqlx/blob/main/FAQ.md#how-can-i-bind-an-array-to-a-values-clause-how-can-i-do-bulk-inserts)). Some testing would need to be...

Apart from theming, which would be super nice, the window decoration does not integrate well into windows. For example, I would have expected being able to drag it to the...

Awesome! For `ts-rs`, we pretty often do *technically* breaking releases, but for most users, they are actually drop-in (unless e.g they implement `TS` manually). For the CLI, we probably want...

> - [ ] Explore a way of generating an `index.ts` file to reexport all the generated types - We could, after `cargo test` finishes, walk the output directory and...

> add a cargo feature that blocks test generarion, so users would do cargo test --features ts-rs/export or something like that I like that! > This would need to be...

> Awesome! I'll work on that later today, what do you think the feature should be called? Oh, I'm terrible with names. But `export` seems reasonable :D

> Do you think we should gate only the test generation behind the feature or should we make the whole #[derive(TS)] a no-op? I considered both, but I think making...

Getting [#49359](https://github.com/rust-lang/rust/issues/49359) would be pretty cool - we could parse the JSON output, and do interesting stuff with it. ```json $ cargo +nightly t --features ts-rs/export -- -Z unstable-options --format...