Skip to content

Feature Request: Support nested includes for list rule conditions (?include=rules.conditions) #1438

@Benechi

Description

@Benechi

Problem

?include=rules on the list collection endpoint returns rule container objects with no condition detail. Fetching condition logic requires a separate API call per rule, per list.

Proposed Solution

Support nested includes — e.g. ?include=rules.conditions — so full filter logic is returned in a single request at the collection level.

Why It Matters

A full audit of all list filter logic currently requires ~150 sequential API calls. With nested includes this would be 1–2 calls.

Current Workaround

Loop every list → every rule → fetch conditions individually. Works but is slow, burns rate limit, and makes real-time auditing impractical.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions