There is a bug with relation parameter name in URLs

[ozziest]

Problem

• PATCH /api/v1/customers/:id
• PATCH /api/v1/customers/:parentId/employees/:id
• DELETE /api/v1/customers/:parentId/employees/:id
• POST /api/v1/customers/:parentId/employees/:parentId/children

We can't use parentId multiple times in URL. We can't find the correct parameter for the correct model.

Expectation

• PATCH /api/v1/customers/:id
• PATCH /api/v1/customers/:customerId/employees/:id
• DELETE /api/v1/customers/:customerId/employees/:id
• POST /api/v1/customers/:customerId/employees/:employeeId/children

We should use the following pattern;

• Model name (singular version) + model primary key
• It should be camelCase

Examples

• User.id -> userId
• User.uuid -> userUuid
• UserTag.ud -> userTagId

Tech Details

• RouteBuilder:130
• Instread relation.foreignKey
  • relationModel.name+relationModel.primaryKey
  • Example: User.id => userId
  • Example: UserTag.uuid => userTagUuid

Addition: We should check request.params usage in the whole library.