Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(ng-add): do not throw if custom builder is used for "test" #14203

Merged

Conversation

devversion
Copy link
Member

  • No longer throws an exception if someone runs ng-add but uses a custom builder for the test target. Since theme files are not necessarily mandatory for running tests, we should just show a warning instead of exiting the whole ng-add process.

Fixes #14176

* No longer throws an exception if someone runs `ng-add` but uses a custom builder for the `test` target. Since theme files are not necessarily mandatory for running tests, we should just show a warning instead of exiting the whole `ng-add` process.

Fixes angular#14176
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Nov 19, 2018
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 19, 2018
Copy link

@FrozenPandaz FrozenPandaz left a comment

Choose a reason for hiding this comment

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

LGTM, satisfies the requirements. Thank you very much!

src/lib/schematics/ng-add/theming/theming.ts Show resolved Hide resolved
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Nov 28, 2018
@jelbourn jelbourn merged commit ee45aab into angular:master Nov 28, 2018
@devversion devversion deleted the fix/ng-add-not-throw-test-changed branch November 28, 2018 09:21
jelbourn pushed a commit that referenced this pull request Dec 3, 2018
* No longer throws an exception if someone runs `ng-add` but uses a custom builder for the `test` target. Since theme files are not necessarily mandatory for running tests, we should just show a warning instead of exiting the whole `ng-add` process.

Fixes #14176
josephperrott pushed a commit to josephperrott/components that referenced this pull request Jan 14, 2019
…ar#14203)

* No longer throws an exception if someone runs `ng-add` but uses a custom builder for the `test` target. Since theme files are not necessarily mandatory for running tests, we should just show a warning instead of exiting the whole `ng-add` process.

Fixes angular#14176
@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 10, 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: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Downgrade non-default builders error to warning
5 participants