Steven Chu

Hello! I was originally hoping to tackle some of this but all I've gotten to so far is just bumping the version numbers in all the various `Cargo.toml` files; but...

One thing I could think to do is `cd` into each of the workspace crates individually and try building those? Seems like a relatively parallelizable way to do this migration?...

> The correct way to build a single crate in a workspace is `cargo check -p lemmy_db_views`. Doing it with cd might not work correctly. > > The error with...

Sigh I'm afraid I may have bitten off more than I can chew at the moment; the main thing that makes me say this is that from the root dir,...

Thanks to both! Okay I'll take another stab at this this weekend -- will try bumping `diesel-derive-newtype` > Also besides newtype, run cargo +nightly fmt before each commit, because there...

> I was able to apply the upgrade to diesel-derive-newtype 2.0.0-rc.0 on your branch. This fixes most of the errors in db_schema, only a few remain (and tons of warnings)....

> Any update on this? Ah sorry unfortunately things got crazy and I took a new job 😅 and haven't had much time. I don't know how far this branch...

EDIT: It looks like the `do_nothing()` method allows access to the target (in the examples below is `ConflictTarget((name, hair_color))` and `ConflictTarget(name)` so I'm guessing it's feasible (I dunno if I...

> Thanks for working on this 👍 This already looks quite good. I've left a few comments where things needs some improvements. Otherwise I've added some basic ideas how to...

> I've tried to allocate some time for this this week, but failed to do that. Hopefully I'm able to add a few more in depth comments next week here....