feat(docs): Normalize documentation and enrich text rendering - #31
Merged
Merged
Conversation
Resolve documentation links and exact fetch destinations while retaining raw response data. Render sparse pages, all supplied declarations, availability qualifiers, and safe reference text without terminal UI dependencies.
philprime
marked this pull request as ready for review
September 24, 2026 18:19
philprime
enabled auto-merge (squash)
September 24, 2026 18:19
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.
Extract documentation normalization and client improvements from
feature/tuiwhile keeping the CLI noninteractive. Sparse pages, resolved references, all supplied declarations, and availability qualifiers now feed human text rendering. Exact-path requests preserve path spelling and fetched documents retain their canonical destinations and original response data.Scope
Independent of the search PR. No SwiftTUI dependency, repository-wide client migration, deployment-target increase, or output-flag changes. Raw
types view --jsonremains on the existing raw renderer.Verification
Decoder, destination, exact-path, canonical-root, renderer, and runner tests passed, along with
make test,make analyze, andmake build. Live release checks rendered Swift String as text and retained its upstream JSON metadata shape.