rest_api: Allow multiple resolve params in an endpoint config about verified-sources HOT 4 OPEN

For sure! <assignment_id> is a child of <project_id> in a one-to-many relationship -- each project has many assignments, but each assignment belongs to only one project.

Edit: If it helps, the assignment endpoint relies on project_id as well, it's just the first part of the subtask endpoint -- /api/v1/projects/<project_id>/assignments

from verified-sources.

I'll add another vote to this enhancement! Currently working with an API that wants two different IDs in the endpoint to return subtask data:

/api/v1/projects/<project_id>/assignments/<assignment_id>/subtasks

from verified-sources.

Hey @jecolvin thanks for the input. Could you please share how <project_id> and <assignment_id> are related? dlt needs to figure out how to iterate over both <project_id> and <assignment_id>.

from verified-sources.

@burnash Followup on my work and a proposal for a v1 of this feature:

I discovered I could get the project_id form the assignment endpoint, it was just named differently than I expected (assignable_id). So I could populate both params using a single resource. Relevant code:

    @dlt.transformer(data_from=assignments, write_disposition="replace")
    def subtasks(assignments):
        @dlt.defer
        def _get_subtasks(_assignment):
            project_id = _assignment["assignable_id"]
            assignment_id = _assignment["id"]
            for page in client.paginate(
                path=f"projects/{project_id}/assignments/{assignment_id}/subtasks",
                params={"per_page": 250},
            ):
                yield page

        for _assignment in assignments:
            yield _get_subtasks(_assignment)

That might be a good v1 for multiple resolve params: You can declare multiple resolve params as long as they all come from the same resource. That way it should still be a single, straightforward transformer.

from verified-sources.