Skip to content
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.

Sign up for GitHub

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

Jump to bottom

The Response should always be a List #340

Open
8 tasks
mekhlakapoor opened this issue Feb 7, 2025 · 0 comments
Open
8 tasks

The Response should always be a List #340

mekhlakapoor opened this issue Feb 7, 2025 · 0 comments

Comments

@mekhlakapoor
Copy link
Contributor

mekhlakapoor commented Feb 7, 2025 •
edited
Loading

User story

As a user, I want the response.data to always be the same data type. Currently, the ModelResponse handler checks if the length of aind_models is 1, and if so returns the data as a dictionary,

Acceptance criteria

  • Given a response, return a list models
  • Update tests for all endpoints as necessary

Sprint Ready Checklist

  • 1. Acceptance criteria defined
  • 2. Team understands acceptance criteria
  • 3. Team has defined solution / steps to satisfy acceptance criteria
  • 4. Acceptance criteria is verifiable / testable
  • 5. External / 3rd Party dependencies identified
  • 6. Ticket is prioritized and sized

Notes

Add any helpful notes here.
@mekhlakapoor mekhlakapoor changed the title The Response should always be a list The Response should always be a List Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mekhlakapoor