Skip to content
This repository was archived by the owner on Apr 2, 2025. It is now read-only.

Conversation

@theodorehreuter
Copy link
Contributor

@theodorehreuter theodorehreuter commented Feb 4, 2025

To meet the goal of having all pagination features fully contained within the POST body for search_opportunities the OpportunityRequest POST model has been updated to include a limit and 'next` field. PR changes here are accounting for and handling the downstream effects of that model change - updating the endpoint and tests.

Related Issue(s):

Proposed Changes:

  1. Adding a next and limit field to the OpportunityRequest POST body model.

PR Checklist:

  • I have added my changes to the CHANGELOG or a CHANGELOG entry is not required.

…o token are in POST body, and changed tests and implementation to refelct this change in the model
"limit": limit,
}
links.append(self.pagination_link(request, body))
search.next = pagination_token
Copy link
Contributor Author

@theodorehreuter theodorehreuter Feb 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice side effect of model change is that limit stays the same and just get carried through and all we have to update is the new pagination token for the returned body in the link object.

Copy link
Contributor

@philvarner philvarner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one minor comment

@theodorehreuter theodorehreuter merged commit 8baad02 into main Feb 5, 2025
3 checks passed
@theodorehreuter theodorehreuter deleted the tr/fix/search_opportunities_body branch February 5, 2025 16:10
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants