Post

nunomaduro
nunomaduro@enunomaduro·
I've been toying around with this idea of making the "explain" queries in @laravelphp better. You know how we usually grab the SQL query from Eloquent and EXPLAIN it in MySQL? Well, I thought, why not simplify the whole thing by adding "explain()->dd()". What do you think? 👇🏻
nunomaduro tweet media
English
16
15
223
19.1K
Greg Korba 🛠️🛹 Codito
Greg Korba 🛠️🛹 Codito@_Codito_·
@enunomaduro @laravelphp I think exactly the same as about the whole `Dumpable` idea: twitter.com/_Codito_/statu… dd(User::first()->chirps()->explain()); 🤷‍♂️
Greg Korba 🛠️🛹 Codito@_Codito_

It's NOT your class' responsibility to dump itself. Dumping class is not something that should be part of production code. Chained call is not an argument for bloating class with a trait. When using `symfony/var-dumper` you can use `dump()` and `dd()` directly anywhere 🤷‍♂️.

English
3
0
9
876
Fabien
Fabien@xBafS·
@_Codito_ @enunomaduro @laravelphp I hope they will reconsider the Dumpable thing but it's just in the continuity of adding vertical bloat to every class and couple everything together more. #issuecomment-1556142283" target="_blank" rel="nofollow noopener">github.com/laravel/framew…
English
1
0
0
29
Paylaş