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
{{ message }}
This repository has been archived by the owner on Jan 2, 2018. It is now read-only.
Hi!
Thank you for the DSL/library; it's going to be incredibly useful to me and a lot of people.
Is there currently any way to describe the API as a whole (meta-information; such as what the API is intended to be used for, what are the different available processes, etc.)?
I think such information could prove valuable for middle to large APIs to see how the different 'services' fit together. What are your thoughts on it?
The text was updated successfully, but these errors were encountered:
That's a great idea. I'm not quite sure where that should live tho and that's probably why I was only providing end point specific documentation. Do you have a suggestion to provide more global documentation?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi!
Thank you for the DSL/library; it's going to be incredibly useful to me and a lot of people.
Is there currently any way to describe the API as a whole (meta-information; such as what the API is intended to be used for, what are the different available processes, etc.)?
I think such information could prove valuable for middle to large APIs to see how the different 'services' fit together. What are your thoughts on it?
The text was updated successfully, but these errors were encountered: