We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attachment: Download
md5: 017fab3f29d8a315c4481d90fb1ec6c1
Issue Description:
Summary: When I subclass a class defined in another module, the “Inherits from” relationship field is listed on the page but its blank.
The `targetFallback` does appear in the symbol graph like it does for protocol conformance, so this appears to be a DocC bug, not a symbol graph bug.
I'd expect the behavior for subclassing here to match the behavior for protocol conformance.
"relationships": [ { "kind": "conformsTo", "source": "s:3Foo0A5ClassC", "target": "s:3Bar0A8ProtocolP", "targetFallback": "Bar.BarProtocol" }, { "kind": "inheritsFrom", "source": "s:3Foo0A5ClassC", "target": "s:3Bar0A5ClassC", "targetFallback": "Bar.BarClass" } ]
Notes: Attaching the full symbol graph for this project along with a reproducing Swift package.
The text was updated successfully, but these errors were encountered:
Comment by Daniel Grumberg (JIRA)
This has been resolved in #95
Sorry, something went wrong.
No branches or pull requests
Attachment: Download
Additional Detail from JIRA
md5: 017fab3f29d8a315c4481d90fb1ec6c1
Issue Description:
Summary:
When I subclass a class defined in another module, the “Inherits from” relationship field is listed on the page but its blank.
The `targetFallback` does appear in the symbol graph like it does for protocol conformance, so this appears to be a DocC bug, not a symbol graph bug.
I'd expect the behavior for subclassing here to match the behavior for protocol conformance.
Notes:
Attaching the full symbol graph for this project along with a reproducing Swift package.
The text was updated successfully, but these errors were encountered: