Conversation
Take documentation links from information in Apple's documentation bundle. We statically know that these are correct.
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
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.
Use the
apple-doccrate I introduced in 0dd51d5 to parse the data that Xcode's documentation viewer uses (this is the same data as on https://developer.apple.com/documentation), and use that inheader-translatorto enhance the documentation we emit.Fixes #309.
TODO:
cargo run --bin header-translator --release -- allnow takes quite a bit longer.As an example of how this would look, compare the documentation for
NSVisualEffectViewon Apple's website with what it would be inobjc2-app-kitafter this PR: