This is a package that was inspired by one of the Laravel project i worked on recently that required me to run over half a dozen different updates on one particular Model or Entity. I could have easily created a different controller method and route for each request but it made my web.php file bloated and so was my controller and am a big fan of keeping my routes file as thin as possible and my controllers looking the same as it was when i first ran the artisan make:controller command, containing nothing else but the index, store, show, edit, update, destroy methods. So i decided to look for a way to process different but similar form requests from one controller method and Laravel Form Processor was what i could come up with.

https://tsommie.github.io/laravel-form-processor/

https://github.com/tsommie/laravel-form-processor

I need experienced contributor!!!

anitchec:
This is a package that was inspired by one of the Laravel project i worked on recently that required me to run over half a dozen different updates on one particular Model or Entity. I could have easily created a different controller method and route for each request but it made my web.php file bloated and so was my controller and am a big fan of keeping my routes file as thin as possible and my controllers looking the same as it was when i first ran the artisan make:controller command, containing nothing else but the index, store, show, edit, update, destroy methods. So i decided to look for a way to process different but similar form requests from one controller method and Laravel Form Processor was what i could come up with.

https://tsommie.github.io/laravel-form-processor/

https://github.com/tsommie/laravel-form-processor

1.2.1. Creating a form Process class
Let’s assume you have a model in your Laravel app called Article and you wish to run an update on it to change its published field from false to true, after configuring the directory you wish to place you’re Processes in, run:
please fix doc .

webdeveloperqx:


1.2.1. Creating a form Process class
Let’s assume you have a model in your Laravel app called Article and you wish to run an update on it to change its published field from false to true, after configuring the directory you wish to place you’re Processes in, run:
please fix doc .

Thanks for your observation...please kindly let me know what exactly is missing in the doc to enable an effective fix.

you won't believe i am yet to understand the purpose of this laravel framework and all other PHP frameworks

Greene66:
you won't believe i am yet to understand the purpose of this laravel framework and all other PHP frameworks

LMAO!!! Well do you understand HTML frameworks like Bootstrap or Zurb Foundation or the Jquery library for Javascript? Then Laravel, Symfony e.t.c. are just that for PHP but if you dont then am going to breaking down as easy as possible without writing a bible verse.

Think of any framework as a bunch of code snippets bundled in a folder to enable you write codes that would normally take you days to write yourself, and that's assuming you know what your doing, if you don't you'll end up on Google asking questions like "How do i change a div color from red to blue using javascript or css or any web language for that matter" and that's just one half of it, the other half is wondering what is the best approach to follow and not to mention consistency. Frameworks get all that drama out of the way and reducing 10 to 20 lines of code to just 2 or 1 which lets you focus on your project.

Trust me, a few months spent learning a framework of any kind will save you time and data in the long run.

Not getting enough love people...is there no one who can contribute?