This thread will be used going forward for updates and releases for EveKit. Things are still somewhat fluid in the ESI. You can expect regular updates as we incorporate new/modified ESI endpoints into EveKit. The next upcoming change is documented below.
ESI 2018.04.30 UPDATE on 2018.05.05 at 0000 UTC (midnight 2018.05.04)
We’ll be updating EveKit from the ESI as it stood on 2018.04.09 to the ESI as it now stands on 2018.04.30. EveKit uses the ESI Java client released here which is distributed via Maven releases tagged by date. So in this particular case, we’re moving to the 22.214.171.12480430 release of the enterprises.orbital.eve.esi.client package.
This update has a number of important changes. Please see the release notes below.
The chat channel endpoints have been moved to legacy. As of this release, we will no longer synchronize against these endpoints. Also, the corresponding ESI scope will be removed from any accounts that had it. We will retain any data we already synchronized and make it available in its current form until (or if) new chat channel endpoints are released.
Contact labels for corporations are now supported for the ESI. We have enabled this support in EveKit. As of this release, if your scope allowed access to corporation contacts, we’ll now start synchronizing and storing contact labels as well.
The wallet journal endpoints received a few new fields while eliminating a few others. The new fields are context_id, context_id_type and description. These fields replace (to a degree) first_party_type, second_party_type and all the “extra info” fields. It turns out there are logical mappings to context_id for most of the fields in “extra info” except for npc_id and npc_name. To preserve as much data as possible, we are therefore populating historic description fields with the string “first=<first_party_type> second=<second_party_type> npc_id=<npc_id> npc_name=<npc_name>”. Many of these values will be NULL. The remaining fields will be copied to context_id (with a corresponding setting in context_id_type) according to the table below.
|If this “extra info” field is set…||then it will be copied to context_id and context_id_type will be set to this value…|