You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We will likely adjust the schema going forward once design has figured out what they want to display, but we want the data to be a list of "mini" opportunity objects. We do not want the full opportunity, but just a few top fields that a user has. For now we'll just put the ones above
Acceptance criteria
Schema created
Dummy endpoint which returns a static response created
The text was updated successfully, but these errors were encountered:
chouinar
changed the title
Create GET /users/saved-opportunities API schema
Create GET /users/:userId/saved-opportunities API schema
Dec 18, 2024
chouinar
changed the title
Create GET /users/:userId/saved-opportunities API schema
Create GET /users/:userId/saved-opportunities API schema and stub endpoint
Dec 19, 2024
Summary
There is no request body, the user ID is in the URL.
We want to return a list response like so:
We will likely adjust the schema going forward once design has figured out what they want to display, but we want the data to be a list of "mini" opportunity objects. We do not want the full opportunity, but just a few top fields that a user has. For now we'll just put the ones above
Acceptance criteria
The text was updated successfully, but these errors were encountered: