jonobrien / evetournaments.com

parse EVE Online CREST Tournament data

eve-tournaments

"The deadline in question is May 8th, 2018. On this date, we’ll be shutting down the XML and CREST APIs. Team Tech Co does not take this decision lightly, and we want you to understand why we have made this decision." source no mention of tournament parity...

Originally this was just going to be a demo showing some public CREST API data, and a possible use case for it. Since then CCP announced the ESI API which will replace both the CREST API and the older XML API. CCP AquarHEAD replied with a possibly different direction for the endpoints moving forward. So if/when something happens and the data is updated for ESI, I will update and make this demo more legitimate. CCPlease.

Displaying public CREST data grouped by endpoint

$ npm install
$ node server.js

endpoints

• /tournaments/

• /tournaments/teams/<id>/

• /tournaments/<id>/series/

• /tournaments/<idX>/series/<idY>/matches/

• Eventually contributed to the docs

• will migrate to ESI api when CCP migrates Tournament endpoints. Facelift to happen CCPSoon(tm)

• also hosted on gh-pages

CCP Developer License

evetournaments.com's Issues

revert to dropdown for matches

this commit

because I broke something somehow 👍

This will also fix the rows being oddly spaced when popups and dropdowns are populated. Viewing matches as popups did that anyway.

viewing replays

https://www.reddit.com/r/evetech/comments/50udaw/evedevs_yc1188_crest_features_ccp_bartender/?ref=share&ref_source=link

refactor query workflow

every query of the api has:

check for cache
query if not cached
parse data

done separately for each, should generalize this method into single function

esi pagination, plus full parity CCPSoon

https://developers.eveonline.com/blog/article/esi-concurrent-programming-and-pagination

assuming tournament data is eventually migrated to the ESI swagger endpoints, hopefully it is paginated. CCPLEASE

refactor into second table

popups should just be in another table, it's too much to have in a popup/dropdown, etc. etc.

ESI API

this beauty, 18 months, all XML and CREST in 1.
https://developers.eveonline.com/blog/article/introducing-the-esi-api

image server migration

https://developers.eveonline.com/blog/article/from-image-server-to-a-whole-new-image-service-1

real rate-limit avoidance

move ajax calls into server, add user-agent, make CCP happy.

gg ccp

rip everything