It would be nice if the response from /universe/structures/{structure_id}/ would return the ID of the structure being queries structure_id.
Use case
When writing an application that deserializes the response of /universe/structures/{structure_id}/ into an object it's messy to have to manually "add" the structure_id to object instead of it being populated as part of the deserialization process
Authentication
This would be modifying the existing route that uses scope esi-universe.read_structures.v1
Example return
Propose what an example return might look like. E.g.:
GET /universe/structures/123456789/?datasource=tranquility
Feature Request
It would be nice if the response from
/universe/structures/{structure_id}/
would return the ID of the structure being queriesstructure_id
.Use case
When writing an application that deserializes the response of
/universe/structures/{structure_id}/
into an object it's messy to have to manually "add" thestructure_id
to object instead of it being populated as part of the deserialization processAuthentication
This would be modifying the existing route that uses scope
esi-universe.read_structures.v1
Example return
Propose what an example return might look like. E.g.:
GET /universe/structures/123456789/?datasource=tranquility
Checklist
Check all boxes that apply to this issue: