You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Windows 7, 64-bit (using Node v6.9.0, FF, angular2 v2.23, angular-cli v1.0.0-beta.22-1, typescript v~2.0.3) I get the error message
Exported parameter ValueCheckingMode has or is using private name ('Anonymous class').
when trying to ng serve a project using json2typescript package. Tried it with SALSAH (using json2typescript v0.9.3) and a completely new TestApplication as described in the README here (with latest v0.9.5).
Changing
public static ValueCheckingMode = class {
to
public static ValueCheckingMode: any = class {
did the trick, but I'm not sure whether it is the best possible type nor solution. It's somehow connected to this old TypeScript issue.
On MacOS X (also Node v6.9.0., FF) I could not reproduce this error, it's running without problems.
The text was updated successfully, but these errors were encountered:
Sorry for the late reply, I had to wait upgrading typescript or angular-cli for several reasons. And thanks for the hint, with angular-cli 1.0.0-beta.30.0 I don't get the error anymore.
I've opened a request to fix issues like these in TypeScript by bringing declaration files to parity with language features. microsoft/TypeScript#35822
On Windows 7, 64-bit (using Node v6.9.0, FF, angular2 v2.23, angular-cli v1.0.0-beta.22-1, typescript v~2.0.3) I get the error message
when trying to
ng serve
a project usingjson2typescript
package. Tried it with SALSAH (using json2typescript v0.9.3) and a completely new TestApplication as described in the README here (with latest v0.9.5).Changing
public static ValueCheckingMode = class {
to
public static ValueCheckingMode: any = class {
did the trick, but I'm not sure whether it is the best possible type nor solution. It's somehow connected to this old TypeScript issue.
On MacOS X (also Node v6.9.0., FF) I could not reproduce this error, it's running without problems.
The text was updated successfully, but these errors were encountered: