Nested api controller for fetching child resources

[phpsa]

This method allows us to create a nested child API controller route

• artisan make:api:controller ChildController --parent=Parent
• Confirm both the following methods work for relations in the ChildController
  • protected string $parentModel = Viewing::class;. -- this is where the relation and the url key will be the strtolower of the base classname, ie /api/viewing/{viewing}/notes and in the Notes model the method to get the related record is named viewing
    • should either of the 2 names in the first method be different, then an array can be passed:
      ['relationnameInModel' => 'routeParamName']
  • confirm index method gets only the records related to the specific parent
  • confirm create method auto-adds the id to the created record
  • Show / Update/ Delete should validate based on parent / child

[samatcd]

This is awesome.

Do we have to create a separate controller for each relationship we want to expose in this manner? Could we not simply have a list of models on the parent controller as a basic implementation option (while still support this Parent controller method for more complex situations)?

Just trying to find a way to reduce boilerplate for the 90% use-case where there will be little / no customisation to the controller.

[phpsa]

This is awesome.

Do we have to create a separate controller for each relationship we want to expose in this manner? Could we not simply have a list of models on the parent controller as a basic implementation option (while still support this Parent controller method for more complex situations)?

Just trying to find a way to reduce boilerplate for the 90% use-case where there will be little / no customisation to the controller.

@samatcd - Looked into this,
while a boilerplate option looks easy - it removes some of the finer bits that is inherited from Laravel directly - specifically in the case of the method parameter injections.