JP Simard
JP Simard
See 0xced/XCDYouTubeKit@a86022d > There are still a lot of issues to be solved before jazzy can be used instead of appledoc. (Tested with jazzy 0.6.0) > - No [explicit cross-references][1]...
As of #530, they're rendered in exactly the same way: 
When concatenating sourcekitten runs for different podspec targets, we end up with multiple versions of the same declaration: https://github.com/realm/jazzy-integration-specs/blob/jp-deprecate-swift-1/document_moya_podspec/after/execution_output.txt#L24 This causes incorrect warnings to be displayed, and makes the list...
From https://github.com/realm/jazzy/issues/492#issuecomment-206525836: > As for the `/*!` comment blocks, I just assumed they are supported, because HeaderDoc, Xcode and Doxygen all recognize them.
For example, Alamofire documents declarations in its protocols, but not the implementations of the types inheriting from those protocols. See [URLStringConvertible](https://github.com/Alamofire/Alamofire/blob/1.1.4/Source/Alamofire.swift#L162-L174) as an example.
Instead of passing in a SourceKitten JSON file, jazzy could ingest a DocC archive or the JSON file(s) embedded within as input. This could help users who've invested in custom...
There's something wrong with the podspec configuration.
If set, the resolver will avoid the system's heuristics to only return IPv4 or IPv6 addresses that it considers to be "routable", instead returning all possible IPv4 or IPv6 addresses....
In https://github.com/envoyproxy/envoy-mobile/pull/2018 I disabled remote execution for the kotlin_tests_mac CI job because of test failures that were only occurring when using remote execution but ran fine on GitHub Actions workers...