[api-documenter] Add support for deeply linked types #1326
Closed
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
rbuckton
requested review from
Lincoded,
aditima,
halfnibble,
iclanton,
mpasarin and
octogonz
as code owners
rbuckton
force-pushed
the
deeplyLinkedTypes
branch
from
06ae1ee to
5b7c215
Compare
rbuckton
force-pushed
the
deeplyLinkedTypes
branch
from
5b7c215 to
41d8f27
Compare
Collaborator
|
I'm really excited about this PR, but I haven't had time to look at it yet. I'll aim to get to it this week. Let's get 1317 merged first, though. :-P |
Author
|
Something seems to be wrong with the branch this PR was created from. Closing and recreating. |
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.
From #1317 (comment). This adds support for deeply linked types when emitting to Yaml for DocFX. It does this by utilizing DocFX's support for language-specific type specifications in references.
NOTE: This is based on the work in #1317, which has not yet been merged. There for this PR contains the changes from that PR as well. For the changes specific to this PR, see commit c0d042b.