feat(renderer): Enrich type documentation text output - #16
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Make
types vieweasier to scan with section dividers, boxed availability and Swift code, wrapped prose, and grouped topic links. Render previously omitted overview content, including code examples, nested lists, and callouts, while leaving JSON output unchanged.DocC blocks use typed variants with required content for recognized shapes. Unsupported variants are skipped without weakening the supported models.
Verification
Passed
make test,make analyze, andmake build. Exercised the release command against SwiftUIViewand passed the live SwiftStringtext-rendering integration test.