Jeremy Woertink
Jeremy Woertink
Not sure why I never noticed this before, but we have this method: https://github.com/luckyframework/avram/blob/80311556f0cc2b1186c88c97a74a6494ad87f48e/src/avram/primary_key_methods.cr#L75-L77 This means you can do this ``` user = UserQuery.find(1) user.delete SaveUser.update!(user) ``` The issue here...
Related: https://github.com/luckyframework/lucky/issues/1980 Vite is much faster than Mix, and with Bun about to be default instead of yarn, we might as well do the swap here too. One thing to...
Originally Earthly was added in to help streamline the CI and release flow and clean up a lot of the things like e2e specs, integrations, etc... Plus using earthly means...
I don't know why, but the Windows release flow broke. 
For the last 2 weeks after releasing Lucky 1.4.0, I've noticed an increase in failed CI specs all related to LuckyFlow. Sometimes there's 1 failure, sometimes there's 2... Before finalizing...
This CI run has never worked... https://github.com/luckyframework/lucky_cli/actions/workflows/weekly.yml So we need to either fix it or just remove it.
No clue why, but I almost always see a Flow spec failure, but not always the same error, and it doesn't always fail...
Right now we assume that if there's a `tasks.cr` file, then you must be inside a Lucky app directory https://github.com/luckyframework/lucky_cli/blob/ccaa571765582086d437efe0da4f439a19929d64/src/lucky.cr#L14 Then when you run `lucky -h` you'll get different output...