I am starting to think that developers want these things merged in for the sake of merging in and being seen among contributors. What's so tough of making this as a Request macro or just wrapping request()->all() into an instance of Fluent? Readability is not really a concern here as that could be applied to any "wrapping" of a state.
I see your point but these are just optional things. By adding this, nothing changes except another option to choose from. Laravel’s philosophy has always been about developer productivity and this addition matches that - a lot of pull requests are still closed.
just be as strict as possible, enforce types along the way and return meaningful errors. love the vid tho bro and you have a new sub :)
Appreciate that!
Will ->fluent() work on validated data returned by a form request? Or does it only work on the raw request object?
Great question! I haven’t tried this yet
I am starting to think that developers want these things merged in for the sake of merging in and being seen among contributors. What's so tough of making this as a Request macro or just wrapping request()->all() into an instance of Fluent? Readability is not really a concern here as that could be applied to any "wrapping" of a state.
I see your point but these are just optional things. By adding this, nothing changes except another option to choose from. Laravel’s philosophy has always been about developer productivity and this addition matches that - a lot of pull requests are still closed.