feat: Support inheritance #82
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
Issue #157: mkdocstrings/mkdocstrings#157 Discussion mkdocstrings#536: mkdocstrings/mkdocstrings#536
|
do you have pre visualisation of the docs for this branch somewhere ? Otherwise that is fine I can read the markdown directly |
|
Ah, no, good point. There has been some progress on GitHub's side for offering such a feature natively. In the meantime I could probably use https://github.com/rossjrw/pr-preview-action. |
|
we have smth similar in docarray using netlify : https://github.com/docarray/docarray/blob/d2655238858a7838ca4787187aa9491d4a769e02/.github/workflows/ci_only_pr.yml#L29 |
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.
Closes mkdocstrings/mkdocstrings#157.
Tagging people from mkdocstrings/griffe#170 again: @samsja, @tazend, @cpcloud, @famura, @machow, @gab832, @analog-cbarber, @jayqi, @chrieke, @tristanlatr -> I would love to get your feedback on the docs 🙂 Feel free to subscribe to / unsubscribe from this issue!