azalea/kotlin-fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[Common tests] Use RootDiagnosticRendererFactory for checking messages

Browse Source 
The patch allows checking all diagnostings with checkFullDiagnosticRender().
It is required for the JS BE diagnostic tests.
This commit is contained in:
Alexander Korepanov
2023-09-19 14:09:07 +02:00
parent a7458f18a9
commit 13bd627bfa
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
compiler/tests-common-new/tests/org/jetbrains/kotlin/test/backend/handlers/HandlerUtils.kt
+2 -1
View File
@@ -13,6 +13,7 @@ import org.jetbrains.kotlin.diagnostics.DiagnosticUtils
import org.jetbrains.kotlin.diagnostics.Severity
import org.jetbrains.kotlin.diagnostics.impl.BaseDiagnosticsCollector
import org.jetbrains.kotlin.diagnostics.rendering.DefaultErrorMessages
import org.jetbrains.kotlin.diagnostics.rendering.RootDiagnosticRendererFactory
import org.jetbrains.kotlin.ir.declarations.IrModuleFragment
import org.jetbrains.kotlin.resolve.jvm.diagnostics.KtDefaultJvmErrorMessages
import org.jetbrains.kotlin.test.FirParser
@@ -78,7 +79,7 @@ fun BinaryArtifactHandler<*>.checkFullDiagnosticRender(module: TestModule) {
renderDiagnosticMessage(it.psiFile.name, it.severity, message, position.line, position.column)
}
is FirDiagnosticCodeMetaInfo -> metaInfo.diagnostic.let {
val message = KtDefaultJvmErrorMessages.MAP[it.factory]?.render(it)
val message = RootDiagnosticRendererFactory(it).render(it)
val position = finder.findNextPosition(DiagnosticUtils.firstRange(it.textRanges).startOffset, false)
reportedDiagnostics +=
renderDiagnosticMessage(testFile.relativePath, it.severity, message, position.line, position.column)