Updated sector data about api HOT 8 CLOSED

great work on the companion API, looks like we're building fairly similar things!
Wonder if there's a way we can combine our efforts, the sector data looks great but do you guys have a mapping of the identifiers somewhere?

from api.

@dealloc We don't have a mapping per-se but we have added all planet id's (from your json file) into each sector by taking a look at the in-game map. Then we iterate over the sectors and add it like this:

const planetSector = sectors.find(s => {
  // the index property is the "id" field from the game api
  return s.planets.some(p => p.index === planet.index);
});

We'd be happy to collaborate. We will start working on a front end soon and maybe you can get your hands dirty there.

from api.

Looping over the planet list to find planets in the same sector is interesting
I'll have to see if I can reuse part of that algorithm in this API.

We'd be happy to collaborate. We will start working on a front end soon and maybe you can get your hands dirty there.
While I am proficient in frontend development the aim for this project is to remain an API only.
Would there be changes that could interest you guys in building your frontend on top of this API?

I've been thinking a bit of a rework/redesign of the API might be necessary (as it's currently a very thin wrapper around the base API) and I'm definitely willing to discuss with the community what would work for them

from api.

@dealloc There may be the option to merge our efforts with you and your team as repository member(s) to provide a single source of truth for data retrieval. We have chosen TypeScript to enable collaboration for almost anyone. Next to the abstraction layer we also provide some fancy stuff like:

• Basic, Nested and Multi Filtering
• Pagination
• Sorting
• Field Selection
• Contextual routes e.g /sectors/:id/planets

Check out the postman collection for more information on the endpoints we provide. Would be amazing if we could team up 🚀

from api.

A quick glance indeed learns that the API you guys provide definitely has more "convenience" features built on top of it whereas mine is more of a "wrapper" API around the official one.

Perhaps we could iron out a convenience API (much like yours) and also provide the "official" endpoints for people who transition from using the API directly to a wrapper (eg. less breaking changes).

The primary reason I chose Elixir is that it would allow for fancy features in the future like a websocket connection so people can just get new data pushed to them rather than having to pull information on an interval.

Additionally, how are you guys currently hosting the API? I've just had to upgrade out of the free tier to keep up with traffic, and while the cost is (still) low it's not $0 atm :)

from api.

As you already said well we provide a lot of "convenience" features and additional data. We even added some more cool stuff to the API you might enjoy, take a look at our latest release. Of course your community can gladly use our API (and yes you are free to grab the stratagem data too) 🚀

For us it would be interesting to work together with the other community API maintainers to create a single API that can be used in the long-term and is maintained by the community.

The primary reason I chose Elixir is that it would allow for fancy features in the future like a websocket connection so people can just get new data pushed to them rather than having to pull information on an interval.

PS: I don't foresee and issues with a web socket implementation for our API.

from api.

As you already said well we provide a lot of "convenience" features and additional data. We even added some more cool stuff to the API you might enjoy, take a look at our latest release. Of course your community can gladly use our API (and yes you are free to grab the stratagem data too) 🚀

For us it would be interesting to work together with the other community API maintainers to create a single API that can be used in the long-term and is maintained by the community.

The primary reason I chose Elixir is that it would allow for fancy features in the future like a websocket connection so people can just get new data pushed to them rather than having to pull information on an interval.

PS: I don't foresee and issues with a web socket implementation for our API.

@dealloc Let me know if this is something you would be interested in. You can also contact me on discord at: fabio.nettis

from api.

@fabio-nettis I'd definitely be interested in this.
As you can see we've created https://github.com/helldivers-2 as a community organisation to centralize this sort of development.

Things like the sector information you provided are being centralized under helldivers-2/json to make sharing this sort of information even more accessible to the community.

If you're not already, I recommend dropping in at https://discord.gg/KS8kHVKX and tag me there

from api.