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

Provide written spec #39

Open
Faerbit opened this issue Jun 23, 2015 · 6 comments
Open

Provide written spec #39

Faerbit opened this issue Jun 23, 2015 · 6 comments
Assignees

Comments

@Faerbit
Copy link
Contributor

Faerbit commented Jun 23, 2015

For someone new to this it is very hard to get how the API should behave by only looking at the tests.
I found it difficult to deduce what should happen if you issue a DELETE request to the API root.
I am still unsure how the order property should be handled. Is it completely optional?

Failed tests also do not give helpful information if you do not know how the API should behave.

@moredip
Copy link
Contributor

moredip commented Jun 23, 2015

Thanks for the feedback. It's very helpful to hear from implementers so we can hopefully lower the cost for future implementations.

@Faerbit would you be interested in taking a stab at writing a draft of a spec? Perhaps using something like Swagger?

@Faerbit
Copy link
Contributor Author

Faerbit commented Jun 23, 2015

I'll give it a try in the following days.

@Faerbit
Copy link
Contributor Author

Faerbit commented Jun 28, 2015

I did not really get along with Swagger. The error reporting is kind of bad. So I produced something in Markdown:
https://gist.github.com/Faerbit/baba66c27f95cd0f12ce

@moredip
Copy link
Contributor

moredip commented Jun 28, 2015

This looks good. If you want to add the doc to the site feel free to send a PR. Or I can add it if you'd prefer.

@Faerbit
Copy link
Contributor Author

Faerbit commented Jun 28, 2015

I wouldn't really know where to add it. I would prefer if you would do it.

@moredip moredip self-assigned this Oct 13, 2015
@darrenhaken
Copy link

Any update on whether this got merged? I agree btw that new docs would have been handy for certain things

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

No branches or pull requests

3 participants