Skip to content

Conversation

@crisbeto
Copy link
Member

Fixes some TS errors being logged out when building the schematics due to an outdated path in the exclude and an incorrect mapping in the paths.

@crisbeto crisbeto added pr: merge safe target: major This PR is targeted for the next major release labels Sep 25, 2018
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 25, 2018
"paths": {
"@angular/cdk/schematics": ["../../../dist/packages/cdk/schematics/"]
"@angular/cdk/schematics": [
"../../../dist/packages/cdk/schematics/",
Copy link
Member Author

@crisbeto crisbeto Sep 25, 2018

Choose a reason for hiding this comment

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

@devversion I don't know whether this should still be here. I've left it in for now just in case. Also we have to look into why the CI doesn't fail for these. I took a quick look and it seemed like the TS compilation promise was rejecting as expected.

Copy link
Member

Choose a reason for hiding this comment

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

Yeah this is odd. I assumed there are no "non-breaking" failures because the CI passed and gulp material:build-release:clean as well. I probably just didn't scroll up the whole log because it exited without errors.

Also, yeah, let's remove ../../../dist/packages/cdk/schematics here and just refer to the source. I do not recall why we always refer to dist/packages (in other entry-points of Material)

devversion added a commit to devversion/material2 that referenced this pull request Sep 26, 2018
* Currently if the TS compilation (either through `ngc` or `tsc`) fails, the gulp tasks won't report the error properly because the `reject()` call of the Promise does not have any error message. This causes compilation failures to be ignored. See: angular#13310
@devversion
Copy link
Member

@crisbeto I've found the issue why Gulp didn't report the compilation failures. See #13312. Also everything worked even with errors because the files that failed were just test-cases that weren't referenced anywhere.

Fixes some TS errors being logged out when building the schematics due to an outdated path in the `exclude` and an incorrect mapping in the `paths`.
@crisbeto crisbeto force-pushed the schematics-ts-errors branch from ec1ad83 to 68ed5f8 Compare September 26, 2018 05:52
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Sep 26, 2018
@jelbourn jelbourn merged commit efd2993 into angular:master Sep 26, 2018
jelbourn pushed a commit that referenced this pull request Sep 26, 2018
Currently if the TS compilation (either through `ngc` or `tsc`) fails, the gulp tasks won't report the error properly because the `reject()` call of the Promise does not have any error message. This causes compilation failures to be ignored. See: #13310
roboshoes pushed a commit to roboshoes/material2 that referenced this pull request Oct 23, 2018
Fixes some TS errors being logged out when building the schematics due to an outdated path in the `exclude` and an incorrect mapping in the `paths`.
roboshoes pushed a commit to roboshoes/material2 that referenced this pull request Oct 23, 2018
Currently if the TS compilation (either through `ngc` or `tsc`) fails, the gulp tasks won't report the error properly because the `reject()` call of the Promise does not have any error message. This causes compilation failures to be ignored. See: angular#13310
@angular-automatic-lock-bot
Copy link

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 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: major This PR is targeted for the next major release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants