-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjust GET saved-opportunity endpoint to take in sorting/pagination and use it #3694
Comments
Waiting on frontend changes, @acouch will attempt to resolve by Feb. 19 |
babebe
added a commit
that referenced
this issue
Feb 20, 2025
## Summary Fixes #{[3694](#3694)} ### Time to review: __5 mins__ ## Changes proposed Updated route to POST endpoint to pass in pagination object Added Input schema `UserSavedOpportunitiesRequestSchema` with pagination: can now sort with` "created_at", "updated_at", "opportunity_title", "close_date"` defaulting to `agency_code` Updated service func `get_saved_opportunities ` to implement the pagination and return also return pagination info Updated Test --------- Co-authored-by: Michael Chouinard <[email protected]> Co-authored-by: nava-platform-bot <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Right now the endpoint returns all saved opportunities without any sorting at all. We should add sorting to the endpoint.
The raw column/relationship joins
Acceptance criteria
The text was updated successfully, but these errors were encountered: