Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace references to "icao" with "id" where appropriate #81

Closed
erikquinn opened this issue Nov 10, 2016 · 4 comments
Closed

Replace references to "icao" with "id" where appropriate #81

erikquinn opened this issue Nov 10, 2016 · 4 comments

Comments

@erikquinn
Copy link
Collaborator

erikquinn commented Nov 10, 2016

There are some scattered places where "icao" is used to mean "id", and doesn't really make sense. A quick sweep should be done to rename these.

@erikquinn erikquinn added this to the v3.1.0 milestone Nov 10, 2016
@n8rzz n8rzz changed the title Replace references to "icao" with "id" where appropriate Replace references to "icao" with "indentifier" where appropriate Nov 10, 2016
@n8rzz n8rzz changed the title Replace references to "icao" with "indentifier" where appropriate Replace references to "icao" with "id" where appropriate Nov 10, 2016
@n8rzz
Copy link
Owner

n8rzz commented Nov 10, 2016

would 'identifier' be an appropriate word here, or aircraftId? Better question; when would icao be appropriate?

I would like to reserve the use of id to be used only as a literal id of a class instance.

@erikquinn
Copy link
Collaborator Author

erikquinn commented Nov 11, 2016

Yeah, sorry I didn't mean id necessarily would be the name. But icao makes sense for:

  • ICAO's aircraft type designators (B738, A321, A343, SF34)
  • ICAO's airport designators (KIAD, EGLL, ZSPD, EIDW, LXGB, GMMC)

And that's it, really. It's helpful to use icao as a property when there are multiple possible designators under ICAO's listings as opposed to IATA's. For example, my home airport is {icao: 'KIAD', iata: 'IAD'}, Dublin is {icao: 'EIDW', iata: 'DUB'}, etc.

Other than cases like these, any generalized property name would be appropriate.

@n8rzz
Copy link
Owner

n8rzz commented Nov 11, 2016

awesome, that makes it much clearer. thanks!

@erikquinn
Copy link
Collaborator Author

This issue was moved to openscope/openscope#69

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants