Bugfix/ the compile function hides "data reference not resolved" errors in case of "an operation not implemented" errors #585
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.
Description
Since the
compile
function was designed to serialize theCompilationUnit
, if there is at least one error before serialization, the function must throw an error. However, due to technical reasons, we must serialize theCompilationUnit
before callingCompilationUnit.resolveAndValidate
, which means we might miss information about unresolved data reference errors.To address this issue, the
compile
function has been refactored. If theout
parameter is passed asnull
, it indicates that the method is being used solely for syntax checking. In this case, all errors, including unresolved data references, will be reported before the function throws the final error.Checklist:
./gradlew ktlintCheck
)../gradlew check
).docs
directory.