From 352a44df3fde32e86a7e76dd07039c822bdb8b86 Mon Sep 17 00:00:00 2001 From: Anders Hejlsberg Date: Thu, 31 Jul 2014 15:56:00 -0700 Subject: [PATCH] Accepting new baselines. Previous commit fixes overly aggressive -noImplictAny reporting. In the test case the source of the error is the 'getAndSet' property that implicitly gets type any. The fact that the setter then gets type any isn't actually an error. --- .../implicitAnyGetAndSetAccessorWithAnyReturnType.errors.txt | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/tests/baselines/reference/implicitAnyGetAndSetAccessorWithAnyReturnType.errors.txt b/tests/baselines/reference/implicitAnyGetAndSetAccessorWithAnyReturnType.errors.txt index d6439688597..c3484202590 100644 --- a/tests/baselines/reference/implicitAnyGetAndSetAccessorWithAnyReturnType.errors.txt +++ b/tests/baselines/reference/implicitAnyGetAndSetAccessorWithAnyReturnType.errors.txt @@ -1,4 +1,4 @@ -==== tests/cases/compiler/implicitAnyGetAndSetAccessorWithAnyReturnType.ts (9 errors) ==== +==== tests/cases/compiler/implicitAnyGetAndSetAccessorWithAnyReturnType.ts (8 errors) ==== // these should be errors class GetAndSet { getAndSet = null; // error at "getAndSet" @@ -14,8 +14,6 @@ public set haveGetAndSet(value) { // error at "value" ~~~~~~~~~~~~~ !!! Accessors are only available when targeting ECMAScript 5 and higher. - ~~~~~ -!!! Parameter 'value' implicitly has an 'any' type. this.getAndSet = value; } }