@sarah Perhaps, but in practice the global function calling the app container has never caused any problems for me. And you definitely could inject the config repository where needed, it's just not conventional Laravel. I prefer sticking with conventions.
@heiglandreas That's a fair point, and the default max being discussed is 72 (due to bcrypt internals), so it would not violate the NIST recommendation.
@sarah Every programming decision has trade-offs. I find Laravel to be overwhelmingly positive, despite not being perfect. And in this case, I was doing something dumb, so I'll cut the framework some slack.
@tvbeek got it, that makes sense. So it’s a smoke test that the command runs, you’re not trying to run your tests with the cached environment (though I do recommend running tests with routes cached, I’ll share a bug story tomorrow as to why)
Conference ticket and hotel for @phptek 2024 have been booked. Just attending this time rather than speaking like I did in 2023...and 2016, my first time speaking at a PHP conference.
Thinking back, this will be the first PHP conf for which I have nothing special on my badge (speaker or organizer) since SunshinePHP 2020 (and before that php[world] and JestPHP in 2019). I've attended other confs recently (five this year, in fact), just not PHP ones.
@shawnhooper I think jobs would be okay. The framework should boot fresh on each job execution. I haven’t tested it, but that’s my understanding of how Laravel runs jobs.