It seems most people are using controller or repository based validation and not using models directly.

In regards to model based validation, you could take a look at https://github.com/dwightwatson/validating

dubcanada said:

It seems most people are using controller or repository based validation and not using models directly.

In regards to model based validation, you could take a look at https://github.com/dwightwatson/validating

is this package support for auto-hydration model?

dubcanada said:

It seems most people are using controller or repository based validation and not using models directly.

In regards to model based validation, you could take a look at https://github.com/dwightwatson/validating

watson/validating's package is actually consumed by esensi/model's package so by using esensi/model you get all of the extra bolt on behavior of the http://github.com/esensi/model traits but also Dwight's self-validating models. Esensi/model also backported some ruleset behaviors (will be deprecated eventually as it's not a great use of models) for those looking to bring their Laravel 4.2 and Ardent projects to Laravel 5 without going full-blown into the Request Validator class pattern.