Hey,
it would be nice if we could add keys from the result entry, to the /api/mods endpoint, but with a queryparameter.
So as a user you would add for example: keylist=name,owner,summary,title,thumbnail,tags and it would ONLY give these keys back.
With that we can also get more information that would be needed eventually, without calling each mod's short or long information, which would increase api calls.
Greetz,
Luzifer
[API Request] Option to add specific keys to multi request
- LuziferSenpai
- Filter Inserter
- Posts: 383
- Joined: Tue Jul 08, 2014 10:06 am
- Contact:
Re: [API Request] Option to add specific keys to multi request
Most of the time these requests are served straight from redis cache, so any customisation options here actually increase load on the backend. In general I prefer third party implementations to make a few more api calls in the beginning and then work of their own cache, instead of requesting everything on-demand. This is how Factorio 1.1 works and what the mod portal is optimized for.
bringing the oops to devops
- LuziferSenpai
- Filter Inserter
- Posts: 383
- Joined: Tue Jul 08, 2014 10:06 am
- Contact:
Re: [API Request] Option to add specific keys to multi request
Yea, what I'm working on doesnt allow for a cache, because its a simple HTML page that shows the current "modpack" a user uses.
I wanted to design it to look like the mod portal, but with the data that is currently avaible that is not good, when I would need to request for each mod itself.
But thanks for the answer, I understand the reasoning behind it.
I wanted to design it to look like the mod portal, but with the data that is currently avaible that is not good, when I would need to request for each mod itself.
But thanks for the answer, I understand the reasoning behind it.