Include children_group_ids in /markets/groups/{market_group_id}/

[Blacksmoke16]

Feature Request

Include an array of children_group_ids in the response of /markets/groups/{market_group_id}/

Use case

Would allow easy traversal of a high level market group to iteratively aggergate types belonging to that high level group.

Authentication

A public route, no auth required.

Example return

Propose what an example return might look like. E.g.:

{
    "description": "Capsuleers have several options for modifying their personal capabilities, including cybernetic implants and biochemical boosters",
    "market_group_id": 24,
    "name": "Implants & Boosters",
    "types": [],
    "children_group_ids": [23, 977]
}

Checklist

Check all boxes that apply to this issue:

• Feature request description is provided
• Use case exists
• Feature requires a new route
• Feature adds data to existing route
• Feature requires new auth scope
• Feature can reuse existing scope
• Feature does not require auth
• Meta feature, applies to all routes

[fuzzysteve]

The one thing I'd suggest adding is a top level group. for where there is no parent.

Just to start the tree.

[Blacksmoke16]

I would be ok with that as well. The main reason behind this suggestion is that for a given group_id you have no way to know where in the tree you are, without searching all the other group_ids.

However having the children_ids would allow you to pick an arbitrary group and find the types below it, versus always having to start from the top most group.