Skip to content

build: use ts-api-guardian 0.2.0 - #14287

Closed
chuckjaz wants to merge 1 commit into
angular:masterfrom
chuckjaz:update-api-guardian
Closed

chuckjaz wants to merge 1 commit into
angular:masterfrom
chuckjaz:update-api-guardian

Conversation

@chuckjaz

@chuckjaz chuckjaz commented Feb 3, 2017

Copy link
Copy Markdown
Contributor

What kind of change does this PR introduce? (check one with "x")

[x] Build related changes

What is the current behavior? (You can also link to an open issue here)

Angular used 0.1.4 of ts-api-guardian which used 1.7.3 of TypeScript. Using features introduced after 1.7.3 would produce inconsistent and incomplete guardian files.

What is the new behavior?

Angular now uses 0.2.0 of ts-api-guardian which uses 2.0.10 of TypeScript. This allows correctly guarding apis that use TypeScript 2.0 features.

Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[x] No

@IgorMinar
IgorMinar self-requested a review February 7, 2017 05:59

@IgorMinar IgorMinar left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the diff of this PR looks odd

I would not expect all the dgeni and nunjucks related packages in there.

have you pulled the most recent master and reinstalled your node modules before installing the ts-api-guardian?

the shrinkwrap update process is documented here: https://github.com/angular/angular/blob/master/npm-shrinkwrap.readme.md

@chuckjaz
chuckjaz force-pushed the update-api-guardian branch from 90dd190 to 1114d3b Compare February 7, 2017 18:12
@chuckjaz chuckjaz added the action: merge The PR is ready for merge by the caretaker label Feb 7, 2017
@alexeagle alexeagle removed the action: merge The PR is ready for merge by the caretaker label Feb 8, 2017
@alexeagle

Copy link
Copy Markdown
Contributor

Folding this into the TS 2.1 upgrade PR

@alexeagle alexeagle closed this Feb 8, 2017
@alexeagle alexeagle mentioned this pull request Feb 8, 2017
3 tasks
@angular-automatic-lock-bot

Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants