Update Documenter, fix errors/warnings
#146
Merged
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
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.
#145 included a typo. This PR addresses that, as well as several errors that were slipping by as they were treated as warnings. Bumping to the latest version of
Documentertreats these as errors by default, so they won't be missed in the future.The docstring is removed for the entire
AbstractTreesmodule becauseDocumentererrors if that docstring is not placed somewhere in the docs. As the same info (and more) is covered on the index page of the docs, I assumed it would be safe to remove it from the module file.My apologies for missing the typo in #145. Everything builds locally for me—hoping this resolves these documentation issues in their entirety.