CrUDAG

1. Overview of the Process

Purpose: This flow outlines the process of handling API requests for managing entities, including retrieving all entities, retrieving a single entity by ID, creating, updating, deleting entities, and updating metadata for entities.

2. Key Components and Their Roles

Route:

• Describes the HTTP method and endpoint used to trigger the operation. Example:

  • GET /users: Retrieves all users.

Controller (PrimateController):

• Responsible for managing the API requests and routing them to the appropriate service layer.

Entity Logic:

• Conditional check to determine if specific logic for "all" exists in the entity.

  • Yes: Executes specific logic defined for the entity.

  • No: Calls the service layer.

Service (PrimateService):

• Handles the business logic for the entity's "all" functionality if specific logic is not found in the entity itself.

3. Detailed Description of CRUD Operations

List and explain each CRUD operation mentioned in the diagram, for instance:

• GET /entities - Fetches all entities from the system.

• GET /entities/:id

  - Fetches a single entity by its ID.

• POST /entities - Creates a new entity in the system.

• PUT /entities - Updates an existing entity.

• DELETE /entities - Deletes an entity from the system.

• PUT /entities/:id/metas - Upsert metadata related to an entity.