@enunomaduro It'd be good to have something that perhaps warns if an _at column is detected that isn't past tense, even if the value is a future value. Came across this problem today that caused a mismatch between the scope and the column name.
@jbrooksuk Any plans to handle redirecting old urls? Currently some of the forge cli commands (which are bundled with Herd) return a 404, rendering them useless, the same as the raycast forge extention.
@calebdw That must be a fairly recent change as I've always just moved them to an archive directory instead. I'll have to have a go and see if it works on the few projects that have squashed migrations.
@jbrooksuk@laravelphp Understood, and we do use them, but then it doesn't benefit from any setup that would come from having it installed at point of provisioning.
@freekmurze I use down migrations, but mostly for local dev only. We've all forgotten we needed that extra field on a table, or to add an index. Rather than create a new one to fix the problem, having a down method makes it easy and clean. It can be removed after if needed.
@christophrumpel I've opted to build a simple CLI using Laravel Zero instead, that has some presets but YAML file support per project to do this kind of things. Really does simplify getting devs working across multiple projects quickly and efficiently.
@enunomaduro There is a rector rule that enforces this. And it makes IDE autocompletion a lot easier, less reliant on magic methods and weird typehinting based in whether it actually is running a query or not.
@christophrumpel It would be handy if you had a standalone command that could wrap any other command, such as 'artisan benchmark "run:heavy-command"' allowing for any command to have basic benchmarks run and preventing any stray dev code going into production apps.
@taylorotwell What happens if there are bugs or improvements to the starter kits? We'd then have to re-apply those chnages or fixed back into our app code, rather than there just being a package update to carry out.
@jackmcdade Conditional logic in particular has issues with this. We had a problem recently where a variable was a string, so empty checks worked, but it then shifted to an object with a url() method on, so the condition was always true.