Missing item type for some arrays causes problems with OpenApi generator about api HOT 6 CLOSED

Regarding the waypoints property of the API. It seems that the waypoints are the supply lines, you can see them on https://helldivers.io if you enable the supply lines view

from api.

@Kejax I've experimented with resolving the waypoints, however since it leads to recursive parsing (as all waypoints eventually form up in a circle) it would create a lot of problems.
The only solution then would be to at some level decide to stop rendering waypoints which would make the schema inconsistent (sometimes a planet has waypoints, sometimes it doesn't).

So for the sake of consistency I'm leaving them as planet indexes, someone who needs the waypoints can map them from the indices that are returned from the API.

from api.

@juanlubf can you let me know if your code generator has any more issues regarding schema typing?

from api.

Hi @dealloc , thanks for your fast response. Actually, the code generator now is working perfectly fine after your changes.

However, I'm facing a new issue now, related to some numeric fields. As I said in my previous comment, I'm trying to use this API to build an app in Kotlin, and in Kotlin (don't know if this is the same in other languages), the maximum value for an integer is 2147483647, but in your API there are some fields typed as integer returning values greater than that (e.g. hash), which causes an exception when serializing the JSON. I just changed those fields to type number which translate in Kotlin to a Double. I don't know if this change would be a problem for your implementation.

Fields I had to change from integer to number -> hash, portrait_id_32, message_id_32, title_32

Again, thanks for your time.

from api.

@juanlubf no worries, I've changed all fields that I suspect are internal identifiers (aka _32 fields) to :number which should hopefully get your code generator back on track.

I've changed a few fields you didn't mention as they are not always filled in, so they might've caused problems in the future.

You can check out the details in 9527364
hope this work!

from api.

Seems to be working perfectly!
Thanks!

from api.