These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

BloodlineID or BloodLineID in API

First post
Author
Dragonaire
Here there be Dragons
#1 - 2015-07-20 21:00:29 UTC
So I was just updating Yapeal for the new stuff added to the Eve APIs and I noticed that in CharacterInfo it uses bloodline and bloodlineID but in CharacterSheet it has bloodLine and bloodLineID (Note the small letter vs cap on Line). Is there a reason for this inconsistency or is it just an oversight? This could cause problems for anyone deal with them in say a SQL query on a case sensitive DB or other places where they might be comparing the XML etc. Maybe CCP Tellus can look into this and change it one place or the other for us Blink BTW though it's causing Yapeal to break and making extra work for me currently I'd like to thank CCP Tellus for taking an interest in adding some stuff to the Eve APIs again it felt a little like it was being forgotten with all the stuff being done in CREST. I'd prefer bloodline but either way is fine.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.

CCP Tellus
C C P
C C P Alliance
#2 - 2015-07-20 22:42:45 UTC  |  Edited by: CCP Tellus
Hi,

I found this inconsistency glaring too.

The element bloodLineID matches the existing element bloodLine in char/CharacterSheet.xml.aspx, and the element bloodlineID matches the existing element bloodline in eve/CharacterInfo.xml.aspx.

I opted for maintaining consistency within each endpoint, rather than changing the name of either of the existing elements and risk breaking compatibility.

Hope that makes sense.
Dragonaire
Here there be Dragons
#3 - 2015-07-20 23:07:02 UTC
Glad to see you noticed it too I'm surprised I didn't notice it before or maybe I did and just forgot and never said anything. What you opted for was good just like to see both API be the same which would be better. For most people it probably wouldn't break anything to change one set of them. I think Yapeal is the only library that even tries to validate the XML with an XSD or anything before using it. Most people don't take advantage of case sensitivity for column/table naming in their DB or like MySQL and friends their DB silently change it on you Blink so the chance of it affecting many people is small but it would make the API seem more professional IMHO for what that's worth Smile. Post about this on an IRC channel without any details about who's API etc and the response on the channel was *facepalm*.

Finds camping stations from the inside much easier. Designer of Yapeal for the Eve API. Check out the Yapeal PHP API Library thread.