Skip to content

BUG: rerouting limit with relationship fetching #115

@mannol

Description

@mannol

Hello.

Consider the following:

  • You have 3 resources C
  • Each C resource has 10 relationships R
  • Each R relationship has 10 relationships P

When you request /api/C?include=R.P to fetch all the data at once, the Handler's search method gets called. The search method then receives the following params:

{
  filter: {
    id: ['P_id1', ...] // we get all 100 id's here
  },
  page: {
    offset: 0,
    limit: 50, // you get whatever limit you have set by default
  }
}

If you implemented your search method to respect offset and limit params, you'd never be able to resolve those relationships. So what needs to be done is: jagql should implement paging while resolving relationships. That way, all possible scenarios are covered.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions