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:
Pavel V. Talanov
2017-03-02 17:35:25 +03:00
parent fa58f1b4d7
commit d94da5af40
4 changed files with 50 additions and 1 deletions
@@ -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");