User 'attacks' & 'attacksfull' come back listed by id or slug or whatever you want to call it. They also contain a 'code'.
There is no way to query attacks as far as I can tell. Why do they have slugs and a code? The slugs make sense from an API design perspective because they need to have a unique key in JSON, but what is the code for? It has to be for something, right? Or else why would it be included in a public API? Is an 'attacks' endpoint in the works?
Also, the data from the 'attacks' response is a different shape to the data from the 'attacksfull' response, but with very little difference. The 'attacks' selection has additional fields for attacker/defender names, attacker/defender faction names, chain number, and a modifiers object.
Why? This is bizarre from an API design perspective. If someone could provide me some insight, or has any knowledge on this, it would be very appreciated.
There is no way to query attacks as far as I can tell. Why do they have slugs and a code? The slugs make sense from an API design perspective because they need to have a unique key in JSON, but what is the code for? It has to be for something, right? Or else why would it be included in a public API? Is an 'attacks' endpoint in the works?
Also, the data from the 'attacks' response is a different shape to the data from the 'attacksfull' response, but with very little difference. The 'attacks' selection has additional fields for attacker/defender names, attacker/defender faction names, chain number, and a modifiers object.
Why? This is bizarre from an API design perspective. If someone could provide me some insight, or has any knowledge on this, it would be very appreciated.