Updating docs and fixing API docs on readthedocs #175
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
Pull Request Test Coverage Report for Build 4722ffc4-a474-42ab-b2ce-81adaf5f1b8a
💛 - Coveralls |
This was referenced Oct 13, 2021
Closed
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.
Something changed somewhere about a year ago in a dependency and our API docs haven't been showing up on readthedocs (see Issue #156 ). This PR fixes most of that problem. It cannot display
LightRayor the Ray generator functions yet, though, because right now stableyt_astro_analysisstill uses an old broken reference in yt, and it's hosts the superclass forLightRay. But hopefully this will get addressed when a new version ofyt_astro_analysisis released.While I was at it, I updated the docs to also fix #152 and #173 and generally provide more instructions on how to do stuff.