Put API in tables, add type information #145
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I had to dig into the source code to see what the types and defaults were for the API. This should be documented. I put the data into markdown tables, to make it easier to read. This is something I do for all of my own libraries. However if you don't like the tables, that's fine, but the data still needs to be displayed in some format in the docs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had to dig into the source code to see what the types and defaults were for the API. This should be documented. I put the data into markdown tables, to make it easier to read. This is something I do for all of my own libraries. However if you don't like the tables, that's fine, but the data still needs to be displayed in some format in the docs.