Correctly determine source modules for re-exported symbols for docs #105
Conversation
This file contains hidden or 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
❌ Deploy Preview for bot-core failed.
|
HassanAbouelela
approved these changes
Jul 23, 2022
Member
HassanAbouelela
left a comment
HassanAbouelela
left a comment
There was a problem hiding this comment.
The documentation was built successfully, and the sources all look correct on a quick glance. LGTM
HassanAbouelela
added
a: documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes: #80
In some cases, the origin module of symbols as seen by sphinx doesn't correspond to the actual module they are defined in, this PR makes sure we grab the module where the object is defined in if it's an object we can determine that for.