-
Notifications
You must be signed in to change notification settings - Fork 16
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
[Issue #3447] Create API endpoint for GET /users/:userID/save-searches #3521
[Issue #3447] Create API endpoint for GET /users/:userID/save-searches #3521
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@@ -297,3 +299,22 @@ def user_delete_saved_search( | |||
) | |||
|
|||
return response.ApiResponse(message="Success") | |||
|
|||
|
|||
@user_blueprint.get("/<uuid:user_id>/saved-searches") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should make this a POST endpoint - we might need to add some filters/sorting stuff (design dependent) and that would follow the same search request schema approach as our actual search endpoint.
Probably not that big a deal to switch later, but worth keeping in mind
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call. This will be an easy switch when the requirements arrive.
Summary
Fixes #3447
Time to review: 15 mins
Changes proposed
Create GET endpoint to return saved searched, accounting for enum values
Add unit tests
Context for reviewers
This is the final API required for saving user searches in this iteration.
Additional information
See unit tests