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.

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

As a user, I want the /products end point to work for any class of products #11

Open
tloubrieu-jpl opened this issue Jan 5, 2022 · 1 comment
Labels
icebox p.could-have requirement the current issue is a requirement

Comments

@tloubrieu-jpl
Copy link
Member

@tloubrieu-jpl commented on Thu May 20 2021

Motivation

...so that I am not confused, since currently it always returns empty results:

  • for /products/{lidvid}/collections when lidvid is a bundle
  • or for /products/{lidvid}/bundles when lidvid is a collection

Additional Details

Acceptance Criteria

Given a bundle lidvid
When I perform {{baseUrl}}/products/{lidvid}/collections
Then I expect to get the collections of this bundle as /bundles/{lidvid}/collections does

Given a collection lidvid
When I perform {{baseUrl}}/products/{lidvid}/bundles
Then I expect to get the bundle of this collection as /collections/{lidvid}/bundles does

Engineering Details

this question is the reason why I intially created the ticket NASA-PDS/registry-api-service#32


@tloubrieu-jpl commented on Thu May 20 2021

@jordanpadams this ticket is about the /products/ behavior that I was mentioning at the beginning of the breakout today. You can make your own opinion wither that needs to be updated or not. This is definitely not critical at the moment.

@tloubrieu-jpl
Copy link
Member Author

closed by mistake

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
icebox p.could-have requirement the current issue is a requirement
Projects
Status: ToDo
Development

No branches or pull requests

2 participants