Repository navigation
Conversation
|
Note, this is currently blocked on a TS 2.1-compatible tsickle. |
|
The changes to TypeScript broke |
chuckjaz
left a comment
There was a problem hiding this comment.
Fix or remove ts_plugin.ts
There was a problem hiding this comment.
If set minimum dependency to TS v2.1, then these checking does not necessary.
There was a problem hiding this comment.
But Angular 2.x needs to support TypeScript 1.8 because of semver.
There was a problem hiding this comment.
Oh I see, it's devDependencies in package.json, so there could be a test scenario to simulates TS v1.8 as well?
|
We do test the .d.ts files we publish that they work with TS 1.8
https://github.com/angular/angular/blob/master/tools/typings-test/test.sh#L22
But I think we are missing a test that our JS code executes correctly with
TS 1.8 as a runtime dep
On Thu, Dec 8, 2016 at 10:41 AM Cotton Hou <notifications@github.com> wrote:
*@imcotton* commented on this pull request.
------------------------------
In tools/@angular/tsc-wrapped/src/collector.ts
<#13294>:
@@ -12,6 +12,14 @@ import {Evaluator, errorSymbol, isPrimitive} from './evaluator';
import {ClassMetadata, ConstructorMetadata, FunctionMetadata,
MemberMetadata, MetadataEntry, MetadataError, MetadataMap,
MetadataObject, MetadataSymbolicBinaryExpression,
MetadataSymbolicCallExpression, MetadataSymbolicExpression,
MetadataSymbolicIfExpression, MetadataSymbolicIndexExpression,
MetadataSymbolicPrefixExpression, MetadataSymbolicReferenceExpression,
MetadataSymbolicSelectExpression, MetadataSymbolicSpreadExpression,
MetadataValue, MethodMetadata, ModuleExportMetadata, ModuleMetadata,
VERSION, isClassMetadata, isConstructorMetadata, isFunctionMetadata,
isMetadataError, isMetadataGlobalReferenceExpression,
isMetadataSymbolicExpression, isMetadataSymbolicReferenceExpression,
isMetadataSymbolicSelectExpression, isMethodMetadata} from './schema';
import {Symbols} from './symbols';
+// ModifierFlags introduced in TS 2.1
+// TypeScript prior to 2.1 uses the NodeFlags to store modifiers
+const isStatic = !!ts.ModifierFlags ?
Oh I see, it's devDependencies in package.json, so there could be a test
scenario to simulates TS v1.8 as well?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#13294>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAC5I5YUYomlSN8NDq-PmvhpVfdNKEWVks5rGE9XgaJpZM4LHQfe>
.
|
|
Everyone go on vacation? 😄 |
|
This is blocked on getting angular/tsickle updated to TS 2.1 which is
somewhat harder.
…On Thu, Dec 15, 2016 at 7:35 AM chadbr ***@***.***> wrote:
Everyone go on vacation? 😄
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#13294 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAC5I2IPSQPQzPzFSozrn1MX7j1cwOFRks5rIV4zgaJpZM4LHQfe>
.
|
|
thanks for the update - angular/tsickle#295 |
|
Any news? |
|
We are making progress on a TS 2.1 branch of tsickle right now. |
|
@alexeagle According to the angular changelog typescript 2.1 support came in 2.4.2 or was that only partial support ? |
Note that the duplication in tsconfig.json files will be fixed in a followup CL now that we have tsconfig inheritance BREAKING CHANGE: Angular 4 will support only TypeScript 2.1, so we no longer provide backwards compatibility to TS 1.8.
|
updated to subsume #14287 for ts-api-guardian |
Note that the duplication in tsconfig.json files will be fixed in a followup CL now that we have tsconfig inheritance BREAKING CHANGE: Angular 4 will support only TypeScript 2.1, so we no longer provide backwards compatibility to TS 1.8.
Note that the duplication in tsconfig.json files will be fixed in a followup CL now that we have tsconfig inheritance BREAKING CHANGE: Angular 4 will support only TypeScript 2.1, so we no longer provide backwards compatibility to TS 1.8.
Note that the duplication in tsconfig.json files will be fixed in a followup CL now that we have tsconfig inheritance BREAKING CHANGE: Angular 4 will support only TypeScript 2.1, so we no longer provide backwards compatibility to TS 1.8.
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: