Skip to content

Conversation

ocombe
Copy link
Contributor

@ocombe ocombe commented Nov 14, 2017

Correctly throw xi18n errors (and print warnings) instead of ignoring them.
I've also removed the catch so that the extraction really fails when there is an error.

Fixes #8065

}

const json = stats.toJson('verbose');
if (runTaskOptions.verbose) {
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd prefer we didn't output bundle stats in xi18n since those bundles aren't actually generated on disk and we didn't outputt this information for xi18n before. Can you leave just the warning/error logic please?

@ocombe ocombe force-pushed the fix/#8065-ng-xi18n-errors branch from 3c1ef98 to 963da70 Compare November 14, 2017 11:11
filipesilva
filipesilva previously approved these changes Nov 14, 2017
Copy link
Contributor

@filipesilva filipesilva left a comment

Choose a reason for hiding this comment

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

LGTM, the CI failures atm are due to the view encapsulation changes in master.

@filipesilva filipesilva self-assigned this Nov 14, 2017
filipesilva
filipesilva previously approved these changes Nov 14, 2017
@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 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ng xi18n doesn't report typescript errors
4 participants