Skip to content

Latest commit

 

History

History
68 lines (53 loc) · 4.03 KB

Module-08.md

File metadata and controls

68 lines (53 loc) · 4.03 KB

Module 8: Laravel PHP Framework

Getting Started

Prior to completing the module below it is highly recommended that you look at the following learning material: Even if you consider yourself a Laravel expert, there is material in the resources below that even seasoned users are not unaware of.

You're only building a sample application for the purpose of demonstrating knowledge of the various tools in Laravel. The application concept doesn't need to be something you'd want to show to the world.

The Test

  1. Create a new repository in your GitHub namespace called Laravel-Test, and commit all the work from this module there.
  2. Build a Laravel application with the features, functions, entities etc of your choosing as long as the application meets the criteria below. Be creative and resourceful but at the same time don't take 10 years to build your app.

Application Criteria

When building your application and meeting a specific criteria below, you should use a relevant commit message to indicate that your commit is satisfying a particular criteria.

  1. Build your features using Test First Development. Don't write any feature code until the failing test is created first. 1) Write the test; 2) Write code to make it pass; 3) Refactor; 4) Rinse & Repeat. Keep in mind, however, that you CAN over-test your application. See Test like the TSA by DHH.
  2. Follow the RealPage Louisville Laravel framework development standards. There are a lot of requirements that will guide your development here.
  3. Integrate user authentication.
  4. Integrate sending email (with HTML and Plain Text versions of the email).
  5. All models should have validation. Between all models, make sure to use ALL of these validation rules at least once:
    • Required
      • Numeric
      • Required If
      • Regex
    • Email
    • Url
    • Use a custom error message
    • Custom validation rule
  6. All models should account for mass-assignment vulnerabilities by using the fillable or guarded properties.
  7. Make sure your application is protected from the following security vulnerabilities. The framework may or may not handle some of this for you, so verify to be sure.
    • XSS
    • SQL-Injection
    • CSRF
      • Session-Fixation
  8. Include a minimum of four (4) different Entities (excluding lookups).
  9. Include the following relationships:
    • At least 1 relationship for each model
    • 1+ belongs to relationship
    • 1+ has many relationship
    • 1+ has one relationship
    • 1+ has and belongs to many relationship
    • 1+ polymorphic relationship
  10. CRUD interface for at least 1 model.
  11. Handle uploading an image that is a property of an entity. (Something like $user->avatar). Have 1+ alternative image representations created from the uploaded image (eg. thumbnail, etc.). You may consider using one or more packages to help do this.
  12. Include at least two (2) 'resourceful' routes and controllers.
  13. Subscribe to at least one (1) event. This can be a built-in event or a custom event you fire.
  14. Create at least one (1) Facade.
  15. Use pagination at least once.
  16. Use 2+ Queues: one for sending email (in #5); and one custom queue.
  17. Use at least one query scope in your application.

Wrapping Up

When you are done, push your code to GitHub. Please create a tag called v1.8 with a message of "ready for review". Be sure your tags are pushed to the remote repository and are visible in GitHub.

Create an issue titled Review Module 10 - Laravel PHP Framework and @mention your mentor and team leader.