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
Enhance protocol documentation #85
Conversation
I think the change overall looks pretty good. Two suggestions:
|
e0a9ec4
to
77a849f
Compare
Done. See #98
I am creating a poor man's version of DB's official API docs which follows the same format to try to be somewhat consistent. eg: https://docs.databricks.com/dev-tools/api/latest/account.html#operation/get-credential-configs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM, do we also want to cover the status code in the http response?
NVM, see #98
…Results, and nextPageToken details Added response codes. Fixed formatting. Identified int types. Change error_code to errorCode ID Details ID Drop details Summary 200
Added edge case details with non-negative and 0 max results, and existence of page token.
Fixed JSON formatting.
Identified int types.
https://github.com/delta-io/delta-sharing/blob/c44815eb6b1984e59216e9b7e88b3eeb1b7631db/PROTOCOL.md