Use depth=0 in REST API

To fix the issue with depth=0 in the REST API, follow these steps:

Locate the Query Parameter Handling: Identify where the query parameters are processed in the REST API. This is likely in the controller or service handling the API requests.
Modify Depth Parameter Handling: Ensure that the depth parameter is correctly parsed and handled. If depth=0 is passed, it should be respected and not default to depth=1.
Update the Controller: In the relevant controller file, update the method handling the API request to correctly process depth=0.

Example:

@Get('your-endpoint')
async getYourData(@Query('depth') depth: number) {
  const effectiveDepth = depth === 0 ? 0 : (depth || 1);
  return this.yourService.getData(effectiveDepth);
}

Update the Service: Ensure the service method respects the depth parameter.

Example:

async getData(depth: number) {
  if (depth === 0) {
    // Handle depth=0 logic
  } else {
    // Handle other depths
  }
}

Files to check:

/packages/twenty-server/src/modules/calendar-messaging-participant/jobs/*
/packages/twenty-server/src/modules/calendar/listeners/calendar-blocklist.listener.ts
/packages/twenty-server/src/modules/messaging/blocklist-manager/listeners/messaging-blocklist.listener.ts
/packages/twenty-server/src/modules/messaging/message-import-manager/crons/commands/messaging-messages-import.cron.command.ts
/packages/twenty-server/src/modules/calendar/services/google-calendar-sync/google-calendar-sync.service.ts

Ensure that all relevant parts of the codebase respect the depth parameter.

References

#### About Greptile

This response provides a starting point for your research, not a precise solution. Help us improve! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. [Ask Greptile](https://app.greptile.com/chat/github/twentyhq/twenty/main) · [Edit Issue Bot Settings](https://app.greptile.com/apps/github)

twentyhq / twenty

Use depth=0 in REST API #6101

References