/characters/{character_id}/assets/ - 'unknown location_flag (185)'
Closed this issue · 2 comments
Bug
Some assets returned from /characters/{character_id}/assets/ are not returning their location_flag, instead they are returning an "unknown location_flag (185)" breaking validation of this response data. Interfering with the normal usage of this endpoint.
This is occuring because the respective location flags have not been added to eve-glue, esi/eve-glue#35 is pending review and merge
Request
GET http://characters/character_id/notifications/?datasource=tranquility
Response
Status Code
200
Headers
Logging this issue on behalf of others, I dont have these new ships
Body
[
{
"is_singleton": false,
"item_id": 123456789,
"location_flag": "unknown location_flag (185)",
"location_id": 1234567879,
"location_type": "item",
"quantity": 1,
"type_id": 32458
},
...
Expected
[
{
"is_singleton": false,
"item_id": 123456789,
"location_flag": "InfrastructureHangar",
"location_id": 1234567879,
"location_type": "item",
"quantity": 1,
"type_id": 32458
},
...
Checklist
Check all boxes that apply to this issue:
- Bug description is provided
- Request path is provided
- Response status code is provided
- Response headers are provided
- Response body is provided
- Expected response is provided
I'm also seeing now "unknown location_flag (186)"
on the corporate asset endpoints.
/v5/characters/{character_id}/assets/
and /v5/corporations/{corporation_id}/assets/
Addresses these locations for both Character and Corporation Assets