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.

Sign up for GitHub

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

Jump to bottom

namespace API should return objects #99

Closed
jzelinskie opened this issue Mar 16, 2016 · 2 comments
Closed

namespace API should return objects #99

jzelinskie opened this issue Mar 16, 2016 · 2 comments
Assignees
@jzelinskie
Labels
area/usability related to improving user experience kind/design relates to the fundamental design of a component priority/urgent critical functionality

Comments

@jzelinskie
Copy link
Contributor

In order to future-proof the API for namespaces, we should return a list of objects for the GET route rather than just a list of strings.
@jzelinskie jzelinskie added area/usability related to improving user experience kind/design relates to the fundamental design of a component priority/urgent critical functionality component/api labels Mar 16, 2016
@jzelinskie jzelinskie self-assigned this Mar 16, 2016
@liangchenye
Copy link
Contributor

@jzelinskie , is 'self-assigned mean' you will work on it?
I just worried that multiply people might work on a same feature once we have a roadmap.

@jzelinskie
Copy link
Contributor Author

@liangchenye Yep, I plan to get this out before 1.0, so that if we expand the properties on the namespace object after 1.0, it doesn't break API.

@jzelinskie jzelinskie mentioned this issue Mar 16, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jzelinskie jzelinskie

Labels
area/usability related to improving user experience kind/design relates to the fundamental design of a component priority/urgent critical functionality
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jzelinskie @liangchenye