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
Hi @nickcharlton! I think we'll need a bit of discussion first to determine how best to approach this project, and if my skillset will be useful here.
Initial questions:
First, I see this repo is empty. Did a public REST API for the spacebodies library ever exist? If so, where is that codebase?
I see a total of four routes in the API docs here. Is that correct? Is the current goal to expose these four routes?
I am aware that spacebodies is written in Python. I am most comfortable writing REST APIs in a Node environment, so I would most likely want to proceed that way, especially if I'm the only dev working on this. Do you foresee any problems with that?
Where/how is deployment going to work? Do you have pre-existing infrastructure/servers? If not, is there budget for a PaaS?
I also have finer detail questions, eg:
I see there are a number of arguments on the first two GET routes in the documentation. How did you envision these arguments being passed? As query params? In general, are these docs meant to be taken as rigid requirements, or is the implementation flexible?
But, these specific questions can be opened in separate issues in due time.
The text was updated successfully, but these errors were encountered:
Hi @nickcharlton! I think we'll need a bit of discussion first to determine how best to approach this project, and if my skillset will be useful here.
Initial questions:
spacebodies
library ever exist? If so, where is that codebase?spacebodies
is written in Python. I am most comfortable writing REST APIs in a Node environment, so I would most likely want to proceed that way, especially if I'm the only dev working on this. Do you foresee any problems with that?I also have finer detail questions, eg:
But, these specific questions can be opened in separate issues in due time.
The text was updated successfully, but these errors were encountered: