RFC - Request validation about code-standards

[craigsansam]

I always prefer to use the Request classes to validate and authorise requests before the hit the controller.

IMO leaves less room for accidental changes which cause operations to happen before the request has been validated/authorised.

[Juddling]

I think we're all agreed on just not using Validator::make() unless absolutely necessary, so lets get that written down.

+1 for request classes, here's a good example which encapsulates validation, authorization + determining things about the request:

https://github.com/netsells/leap-web/blob/5cd876862658974d7763f9db9a04f3a7c55ca159/app/Http/Requests/CheckoutWebhookEventRequest.php#L21

[spamoom]

I think ValidatesRequests are appropriate in the right place (when it's a one off and not huge). As soon as we see repetition, request classes are a must

[craigsansam]

I am going to close this RFC on Friday 22nd March and add the outcomes to the coding standards.