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

Figure out API documentation #379

Closed
muneeb-ali opened this issue Apr 4, 2017 · 2 comments
Closed

Figure out API documentation #379

muneeb-ali opened this issue Apr 4, 2017 · 2 comments
Assignees

Comments

@muneeb-ali
Copy link
Member

@jcnelson commented on new data PUT and GET endpoints:

This has stabilized. Where's the best place to document it? The API table we have in the api/README.md file isn't expressive enough, since we need to also document how to construct the inputs and how to parse the outputs.

This opens up the general question that where should we document the API. Options are:

  1. The api_v1.md file that is rendered by the node once it's deployed e.g., at https://core.blockstack.org. We can make that file more visible. It doesn't look very readable on Github though.

  2. api/README.md.

The issue with using #2 is that #1 needs to be there regardless. So #2 will become a mirror and realistically out of sync with time.

Tagging: @jcnelson @kantai @larrysalibra @shea256

@muneeb-ali muneeb-ali self-assigned this Apr 4, 2017
@kantai
Copy link
Member

kantai commented Apr 4, 2017

What if we use a script to generate the api/README.md file from the api_v1.md file or vice-versa? It would solve the syncing problem.

@jackzampolin
Copy link
Contributor

We generate API docs now. Closing this as complete.

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