D: Dependency Inversion Principle - Pass the Parameter as Interface

D: Dependency Inversion Principle - Report Interface

D: Dependency Inversion Principle - Pass the Parameter as Interface

Course Content

Intro

01 What's Inside This Course

Moving Code Away From Controller

02 Moving Validation to Form Request Class

03 Transform Data Before Saving: Mutator or Observer

04 Saving Data: Service or Action Class?

05 Repositories: Why NOT to Use Them?

06 "Background" Tasks: Dispatch Jobs into Queue

07 Dispatch an Event and Let Others Listen to it

08 Repeating Responses: Base Controller or Trait?

09 Global Helpers: Methods That "Don't Fit" Anywhere Else

Practical Examples from Open-Source Projects

10 Eloquent Mutators: 2 Open-Source Examples

11 Service Classes: 2 Open-Source Examples

12 Actions Classes: 2 Open-Source Examples

13 Jobs & Queues: 2 Open-Source Examples

14 Events & Listeners: 2 Open-Source Examples

15 Traits: 2 Open-Source Examples

16 Global Helpers: 2 Open-Source Examples

Architectural Structure: Areas, Modules, Domains

17 Structuring "Areas": Admin vs User - 3 Different Ways

18 Structuring Project into Modules with laravel-modules Package

19 Packages: When Is It Worth Creating Them?

20 Domain Driven Design (DDD): Not Friendly with Laravel?

SOLID Code Structures

21 S: Single-Responsibility Principle - Too Big Methods

22 S: Single-Responsibility Principle - Too Big Controllers

23 O: Open-Closed Principle - Report Formats with New Classes

24 O: Open-Closed Principle - Vendor in Laravel

25 O: Open-Closed Principle - Eloquent Attribute with Salary Calculator

26 L: Liskov Substitution Principle - Type-Hint Everything

27 I: Interface Segregation Principle - Default Laravel Models

28 I: Interface Segregation Principle - Separate Data and Download

29 D: Dependency Inversion Principle - Pass the Parameter as Interface

30 D: Dependency Inversion Principle - Report Interface