The best thing about #Laravel so far is the absence of #XML and #YAML files. All configuration I've seen so far is happening in #PHP files using fluent interfaces.
The worst thing about #Laravel so far is the heavy usage of static and magic methods. Already took me quite some time to find a test failing only when all tests are run, which was caused by caching something on a static variable (not in #Laravel though). And for IDEs to work correctly multiple _ide_helper files are necessary, and even then it is not always working.
@Crell out of curiosity: did you already work on many #Laravel projects? I think the biggest problem is eloquent, but I am trying to go open-minded into this 🙈
@Crell I was already thinking if #Laravel would be nicer to use if you just would not use eloquent, but from the documentation pages I've read until now I've got the feeling that it is so deeply integrated that it might be hard to do so.
Tip for anyone allowing user registrations in your #Laravel app: make use of the extended email validations to catch typos and other email issues up-front. ⚡️
Woke up to discover a shiny new Substack feature: Referrals! 😎
Refer your (dev) friends to Securing Laravel to get on the leaderboard (🤣) and, more importantly, get comp'ed a paid subscription for 1, 3 or 6 months. 🔥
I'm an experienced #freelance#developer, specialized in #PHP / #Laravel. I build new applications, and develop / debug / refactor legacy code. I can also help you with servers and infrastructure.
I am currently available for around 20 hours a week. Fully #remote, or hybrid in the neighbourhood of #Rotterdam, the Netherlands.
I've got a sprint ahead with the goal to implement #mfa on #laravel backend with #vuejs frontend (and another third party app on .NET). The single factor (using #passport with #oauth) exists already (three years in production).
I do not like to use too many dependencies, but obviously doing it all by myself can be a high security risk as well.
However, all "plugins" I found for Laravel usually use their own frontend (blades) as well which I cannot use here.
Any ideas/input/experience on
a) the first steps for migration 1FA -> 2FA
b) using TOTP (which might be less pain for development) or rather FIDO2 (which I'd prefer but do I need to rebuild the whole authentification process?)
Especially mentioning @valorin here, but appreciate any vujes / #quasarframework developer as well ;-)
Finally got around to writing more tests for #Questlog. It's so satisfying when the GitHub actions run so many tests and just turns green.
To be fair, it didn't work right away. Which is good. I found some bugs this way that I didn't have on my machine, but could be a problem on the server.
It's so much easier to write tests for #Laravel with #Pest. I should have adopted this much sooner.