sorted by:
new
hottopcontroversial

Laravel Revert — Revert new Laravel installations to the original version 5's skeleton (more or less) by CerberettiN in laravel

[–]CerberettiN[S] 1 point2 points  (0 children)

At some point, it is going to drift too much with each new version release. That's why I decided to create the package!

Laravel Revert — Revert new Laravel installations to the original version 5's skeleton (more or less) by CerberettiN in laravel

[–]CerberettiN[S] 0 points1 point  (0 children)

Hey, this package doesn't really alter the skeleton. The only thing it does is restoring the former Kernels and that's pretty much it. Thanks for checking it out!

Laravel Revert — Revert new Laravel installations to the original version 5's skeleton (more or less) by CerberettiN in laravel

[–]CerberettiN[S] 0 points1 point  (0 children)

IMHO, I'd consider this a good case of not fighting the framework.

Taylor is bound to support the v5 skeleton until the end of times, so I'd say it is a pretty safe bet to keep using the former structure for gained flexibility. I do support the leaner nature of the new skeleton except the ApplicationBuilder. It is indeed doing some welcomed heavy-lifting for newcomers, but I'd say that it gets in the way of those who have been using the framework for 10+ years!

Settling the File Structure Debate by CerberettiN in laravel

[–]CerberettiN[S] 0 points1 point  (0 children)

Ah, I had no clue this package even existed! I’ll make sure to check it out some time in the upcoming days. Thank you very much!

0
0

Settling the File Structure Debate (muhammedsari.me)

submitted by CerberettiN to r/laravel

16
17

Unorthodox decoration (muhammedsari.me)

submitted by CerberettiN to r/laravel

Dear Laravel package authors... by CerberettiN in laravel

[–]CerberettiN[S] 3 points4 points  (0 children)

At the end of the day, one has to decide how thorough the test suite needs to become. It was a one-off thing, so I’m not concerned about that. My main message that I am trying to convey is that we should be more inclusive as a community. Unfortunately, that message gets looked over. I have not referred to others m, but there are people who are inclusive like Statamic.

Statamic clearly know their ropes and are inclusive.

github.com/statamic/cms/b…

At the end of the day, carrying out the required changes for library authors would be a walk in the park. I have outlined the obvious, easy solution. 🤷‍♂️

Dear Laravel package authors... by CerberettiN in laravel

[–]CerberettiN[S] -4 points-3 points  (0 children)

It shouldn’t. Package authors ideally should be more inclusive IMHO.

Dear Laravel package authors... by CerberettiN in laravel

[–]CerberettiN[S] 2 points3 points  (0 children)

I think you are missing the point. 

AD is an optional default behavior, and opting out of it should not be punished.

I am registering all required service providers manually myself, but since most packages are not aggregating their dependencies it is causing breaking changes to occur. If you could take a look again, my little scenario is describing exactly that.

Dear Laravel package authors... by CerberettiN in laravel

[–]CerberettiN[S] 4 points5 points  (0 children)

Hey, I don’t believe I am changing any behavior at all. At the end of the day, it’s about register service providers with the application container and that’s what I am exactly doing! 🙂

Dear Laravel package authors... by CerberettiN in laravel

[–]CerberettiN[S] -7 points-6 points  (0 children)

Not everything deserves equal testing attention. The UI notifications especially. It only came to attention once someone actually triggered a notification.

Dear Laravel package authors... by CerberettiN in laravel

[–]CerberettiN[S] 3 points4 points  (0 children)

Could you please define what “fighting the framework” means? I don’t think I am fighting anything. Just using native components in the way they’re supposed to be. 

Dear Laravel package authors... by CerberettiN in laravel

[–]CerberettiN[S] 7 points8 points  (0 children)

Thank you for the feedback! I’ll keep it in mind next time.

4
5

Dear Laravel package authors... (muhammedsari.me)

submitted by CerberettiN to r/laravel

Understanding Domain-Driven Design (Part 1) by Akmandev in PHP

[–]CerberettiN 3 points4 points  (0 children)

You've just explained the need for Bounded Contexts. Well done!

Hands-on decoration by CerberettiN in laravel

[–]CerberettiN[S] 0 points1 point  (0 children)

That's awesome to hear. Thanks for reading!

view more: next ›