#503: type references not on classpath displayed as ERROR CLASS #509
Conversation
This file contains 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
… ERROR CLASS Display missing inferred types as the source text
cjbrooks12
force-pushed
the
issues/503
branch
from
e3cb60e
to
c467b60
Compare
|
I've just rebased this branch off the current master (0.10.0) and also added support for inlining the AST text of expressions that could not be resolved normally (such as implicit function/property types) |
|
Dokka has been rewritten since the creation of this PR, please create a new one if the issue persists |
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.
Fixes issue #503: type references not on classpath displayed as ERROR CLASS.
Missing classes used for the bounds of generic methods and for inferred method return types do not seem possible to resolve.