I am using form requests to generate my documentation.
It was working well until I hit a dead-end while working a form request that leverage Laravel dependency injection in the rules method.
I've checked the code where the rules method is called on the form request.
The call is made without parameters.
Thus explaining why the documentation cannot be generated.
I was wondering if there is something I can do with the current state of the library.
If not, it could be nice to have a hook similar for the form request instantiation but for the rules extraction.
I've already tried to use the form request instantiation by changing the DI on my form request but because of the number of parameters used in the extended class, it is not very readable.
It works but it is dirty.
I find it clearer to stick with Laravel DI in the rules method.
Scribe version
4.18.0
Your question
I am using form requests to generate my documentation. It was working well until I hit a dead-end while working a form request that leverage Laravel dependency injection in the
rules
method.I've checked the code where the
rules
method is called on the form request. The call is made without parameters. Thus explaining why the documentation cannot be generated.I was wondering if there is something I can do with the current state of the library. If not, it could be nice to have a hook similar for the form request instantiation but for the rules extraction.
I've already tried to use the form request instantiation by changing the DI on my form request but because of the number of parameters used in the extended class, it is not very readable. It works but it is dirty. I find it clearer to stick with Laravel DI in the
rules
method.Thank you.
Docs