Request for object relation

[jeroenboumans]

Request for object relation

[jeroenboumans]

Whoops, I wasn't aware about the cores entity and what it meant in the context of the rocket. I know now that it's all about the 1st stage? Since these aren't necessarily linked to a specific type of rocket but more to a build, the cores endpoint I specified above can be ignored. Sorry ;-)

[jakewmeyer]

Changes are live, I'll update the wiki shortly

https://api.spacexdata.com/v2/parts/caps?capsule_id=dragon1

https://api.spacexdata.com/v2/parts/caps?capsule_id=dragon2

[jakewmeyer]

First option should be no problem, Don't really know how to aggregate the data to form the second example. I'll look into it further.

Only issue I see is a conflict between different params on the same endpoint, for example:

https://api.spacexdata.com/v2/parts/caps/dragon1
https://api.spacexdata.com/v2/parts/caps/C112

[jeroenboumans]

Perhaps a search param, like the following could to the trick:
https://api.spacexdata.com/v2/parts/caps?capsule=dragon1
https://api.spacexdata.com/v2/parts/cores?capsule=dragon1

I've checked the database and I think it can be done by adding capsule_id to the caps part objects and core parts objects. A ...parts/caps?capsule=dragon1 query can then select all capsules/cores containing this capsule_id. This seems like a one-to-many relationship. Correct me if I'm wrong :)

[jakewmeyer]

I think I understand now, makes sense to add it to caps. What about cores though?

[jeroenboumans]

Thanks Jake!