Laravel VS laravel-explicit-array

Hope this saves a future team from unexpected behavior resulting in (potential) production data loss.

When using Postgres, Laravel's default method for truncate uses the cascade option, which will ignore foreign key constraints and potentially wipe large amounts of data with no confirmation or warning.

It was originally introduced in 2018: https://github.com/laravel/framework/pull/26389/files

Here are two threads on it if you are curious: https://github.com/laravel/framework/issues/29506

I am just exploring middleware in this post, but as you can see this is quite a different approach than we've seen historically. I sat there scratching my head, "How do I set up my own middleware? How do I change the defaults?" I had to explore the Illuminate\Foundation\Configuration\Middleware class to find out.

For example check out this issue I reported on their side: https://github.com/laravel/framework/issues/49089

It does not mean you should absolutely use it everywhere, but it can make sense for your case. Many frameworks, like Laravel use it to compose new projects.

https://github.com/laravel/framework/blob/00894b89e42a9d707c...

Even Tinker is a few lines of code to extend PsySH and credit is barely given.

Taylor Otwell is a fiend for creating wrappers around solid open source libraries, using PHP magic and encouraging bad practices, all just to breed an ecosystem ultimately to land him a Lambo, fuelled by amazing open source foundations that have barely been contributed back to by him.

This same system has been used in Laravel since version 4.0* albeit in the more PHP plain way, using call_user_func_array (Laravel Model Class).

I ultimately had to FORK THE ENTIRE METHODS OF ARR into a separate package because I found out the hard way cannot use macros for altering this behavior.

Take my PR for example, which tried to bring small changes to be able to escape the dot notation in Laravel's Arr. This could have been great if you wanted to use the Arr::set() for keys that contain dots and you do not want them to become nested. Using the $arr['some.dotted.key'] would have been worked but why assign the array directly if Arr::set exists? I couldn't extend the Arr class in a separate package without copy-pasting the entire code from the original Arr since the methods I was replacing are not using other functions that do only one thing, so that I would replace only the methods without the entire logic.