[GH-ISSUE #326] Optimize payload depth property #211

Open
opened 2026-03-03 11:14:05 +03:00 by kerem · 1 comment
Owner

Originally created by @pavanbhaskardev on GitHub (Jul 9, 2025).
Original GitHub issue: https://github.com/dflow-sh/dflow/issues/326

Originally assigned to: @pavanbhaskardev on GitHub.

  • both project, service colloection has bi-directional relationship
  • when fetching project or service with depth, the payload size in increasing
  • decrease the usage of payload-depth and fetch only the necessary details
Originally created by @pavanbhaskardev on GitHub (Jul 9, 2025). Original GitHub issue: https://github.com/dflow-sh/dflow/issues/326 Originally assigned to: @pavanbhaskardev on GitHub. - both project, service colloection has bi-directional relationship - when fetching project or service with depth, the payload size in increasing - decrease the usage of payload-depth and fetch only the necessary details
Author
Owner

@pavanbhaskardev commented on GitHub (Aug 21, 2025):

  1. Removed the depth 10 property
  2. Replaced the depth according to the collection which we're querying
<!-- gh-comment-id:3210504540 --> @pavanbhaskardev commented on GitHub (Aug 21, 2025): 1. Removed the depth 10 property 2. Replaced the depth according to the collection which we're querying
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dflow#211
No description provided.