Nathan G
Nathan G
Using a separate model and table for the invited users solves a few problems: - Encapsulation of invite logic. - Fewer columns on core `users` table. - There are no...
That works too, yep. It still doesn't get around the problem of the converter needing to just kind of 'know' the directory structure around it, but I suppose that could...
Could also work for web clients that still reference the split, right?
You'd remove the web client code before you decide the split? What if you need to quickly reverse the feature? I was thinking about one case in particular where, right...
Yeah after-release or next-release migrations would be my answer there. It's the same kind of feature I'd want for DB schema changes.
Alright, so I can buy that the story around what to do during in-flight rollouts is to not have your TestTrack go a little sideways, and that the small comfort...
My fix was merged into the 'dev' branch, but this repo seems kind of dead lately. As @Theo47 stated, his builds should include those changes. Might be nice for @rallion...
@MonthOldPickle try one of the releases here: https://github.com/Theo47/depressurizer/releases
Hmm, it seems the existing code was already in violation of the line length -- I assume hound only runs on the changed lines? 🤔
(rebased due to file conflicts)