guiguilechat
guiguilechat
that should be another endpoint, eg activities/{userid}/pve/kills/{systemid}/{day} returning for each entity id the number of entity killed. with activities/{userid}/pve/kills/ listing all the (systemid,day)couples that can be used.
Yeah, average of no value is difficult to compute and I also guessed that if the data is not stored in monolith that would not be possible. The second issue...
Maybe add an optional &padding=true parameter to the path to add 0-volume, 0-everything entries to the list ? As I wrote before if the monolith does not know when an...
that's the java code I use once I get sent the new history cache (to create the new list of volumes, sorted by value desc) ``` java List newList =...
close with a won't-fix ?
What he forgot to mention, is that parameter is already present on the regional market path. I personally believe that the correct "fix" would be to remove it from this...
Indeed, market region do not require to check access before returning the cache, therefore they can be cached further from the ESI, while structure market path being authed, the cache-control:private...
> If I want to look up the price of a mining laser there I have to iterate all 73 pages. If I want to monitor that price all day...
IMO it would be better to have 1. a universe/weather/{weather_id} path that returns the information about a weather id (its effect, name among other things) 2. universe/weather/weathers path that returns...
no, you want to split the description of the weather and the relation between systems and weathers in separate paths