You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in v0.8.6 there is inconsistent naming for corporation and corporations in the corporations endpoint, specifically for mining endpoints. Almost all endpoint roots are pluralized (alliances, characters, contracts, etc.) even when they refer to a singular entity. Singularized endpoints are consistently singular. However, for the 3 industry endpoints corporation is singular, in contrast to the other corporations endpoints. This issue can make it difficult to standardize interactions with paths when expecting to find paths sharing the /corporations/ base.
Inconsistency
in v0.8.6 there is inconsistent naming for
corporation
andcorporations
in thecorporations
endpoint, specifically for mining endpoints. Almost all endpoint roots are pluralized (alliances
,characters
,contracts
, etc.) even when they refer to a singular entity. Singularized endpoints are consistently singular. However, for the 3 industry endpointscorporation
is singular, in contrast to the othercorporations
endpoints. This issue can make it difficult to standardize interactions with paths when expecting to find paths sharing the/corporations/
base.Routes
Inconsistent singularized occurrences:
/v1/corporation/{corporation_id}/mining/extractions/
/v1/corporation/{corporation_id}/mining/extractions/observers/
/v1/corporation/{corporation_id}/mining/extractions/observers/{observer_id}/
Consistent, pluralized examples:
/v1/corporations/{corporation_id}/
/v1/corporations/{corporation_id}/alliance_history/
Consistent, pluralized examples that occur in the same Industry group as the inconsistent examples:
/v1/characters/{character_id}/industry/jobs/
/v1/corporations/{corporation_id}/industry/jobs/
Resolution
Change the occurrences of
corporation
tocorporations
to be consistent with the other endpointsChecklist
Check all boxes that apply to this issue:
The text was updated successfully, but these errors were encountered: