Skip to content
This repository has been archived by the owner on Aug 22, 2023. It is now read-only.

Start thinking of API v2 design #70

Open
tcannonfodder opened this issue Jul 24, 2016 · 3 comments
Open

Start thinking of API v2 design #70

tcannonfodder opened this issue Jul 24, 2016 · 3 comments

Comments

@tcannonfodder
Copy link
Member

While Telemachus' API is design is pretty good, there are definitely some use cases where it's not perfect (such as getting specific position data or setting maneuver nodes).

With the potential addition of an camera image endpoint (#69), we should consider a new API design for Telemachus. Version 1 of the API should still be present and work as it does now, but a new version could let us grow Telemachus in some really interesting ways.

@johnmknight
Copy link

What's the best way to post API changes? Would you like them as individual requests or would a list do?
Here's a short list of things I'd like to see (if possible):

  • Crew Information for current vessel (name,stats,etc., also what part/pod they occupy
  • KIS/KAS Mod compatibility (support for inventory,etc.)
  • Science / Data information. Ability to review collected science data from a lab.

@tcannonfodder
Copy link
Member Author

Hey @johnmknight! These are some great suggestions, we can keep discussing them in this issue. 😄

Feel free to fork the repository and work on these changes, then make a PR! Right now I'm working on issue #69, so I'm not sure when I'd be able to work on these enhancements.

@Banbury
Copy link

Banbury commented Jan 11, 2017

A method to get all the information of a vessel in a single object would be nice.

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

No branches or pull requests

3 participants