Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable and creative experience to be truly fulfilling. Laravel attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as:
- Simple, fast routing engine.
- Powerful dependency injection container.
- Multiple back-ends for session and cache storage.
- Expressive, intuitive database ORM.
- Database agnostic schema migrations.
- Robust background job processing.
- Real-time event broadcasting.
Laravel is accessible, yet powerful, providing tools needed for large, robust applications. A superb combination of simplicity, elegance, and innovation give you tools you need to build any application with which you are tasked.
Laravel has the most extensive and thorough documentation and video tutorial library of any modern web application framework. The Laravel documentation is thorough, complete, and makes it a breeze to get started learning the framework.
If you're not in the mood to read, Laracasts contains over 900 video tutorials on a range of topics including Laravel, modern PHP, unit testing, JavaScript, and more. Boost the skill level of yourself and your entire team by digging into our comprehensive video library.
We would like to extend our thanks to the following sponsors for helping fund on-going Laravel development. If you are interested in becoming a sponsor, please visit the Laravel Patreon page:
Thank you for considering contributing to the Laravel framework! The contribution guide can be found in the Laravel documentation.
If you discover a security vulnerability within Laravel, please send an e-mail to Taylor Otwell at [email protected]. All security vulnerabilities will be promptly addressed.
The Laravel framework is open-sourced software licensed under the MIT license.
- JWTAuth
- FormRequest al principio del método
- FormRequest deben ser llamados con el sufijo Request
- La carpeta request debe ir dentro de la carpeta Http
- Los valores de string deben ir entre comillas simples
- Creación de archivo para variables [X]
- Detail (variable en el get del id del recurso) [X]
- Borrado (variable en el get del id del recurso) [X]
- Creación (variables que van por post) [X]
- Actualización (variable en el get del id del recurso y variables por post) [X]
- Autenticación Positivo [5]
- No autenticación cuando la require [6]
A tener en cuenta:
- Hay que crear un test por cada rule de cada variable pasada por post
- Para los métodos de detail, borrado y actualización se debe poder testear tanto con id de recurso valido como invalido
- Cada test debe tener su propio mensaje
A futuro:
- Que los identificadores se escojan solo
- Que los parametros por post se autogeneren en base a las rules
- Tener en cuenta los roles []
- Separar la generación del archivo para parametros de la generación de tests []