Frontend: create component functions for properties with error types
Fixes an inconsistency in light classes where we could have different class structure depending on whether the type was resolved
This commit is contained in:
@@ -4573,6 +4573,12 @@ public class DiagnosticsTestGenerated extends AbstractDiagnosticsTest {
|
||||
doTest(fileName);
|
||||
}
|
||||
|
||||
@TestMetadata("errorTypesInDataClasses.kt")
|
||||
public void testErrorTypesInDataClasses() throws Exception {
|
||||
String fileName = KotlinTestUtils.navigationMetadata("compiler/testData/diagnostics/tests/dataClasses/errorTypesInDataClasses.kt");
|
||||
doTest(fileName);
|
||||
}
|
||||
|
||||
@TestMetadata("extensionComponentsOnNullable.kt")
|
||||
public void testExtensionComponentsOnNullable() throws Exception {
|
||||
String fileName = KotlinTestUtils.navigationMetadata("compiler/testData/diagnostics/tests/dataClasses/extensionComponentsOnNullable.kt");
|
||||
|
||||
Reference in New Issue
Block a user