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(schematics): do not depend on external dependency for colors #17788

Merged

Conversation

devversion
Copy link
Member

Currently we assume that chalk always is installed. This has worked
without any issues for a long time because most CLI projects had chalk
installed. This could potentially change in the projects, or the verison of
chalk could accidentally be older/more recent than what our schematics
expect. We just remove colors and depend on the devkit logger for colors
based on specific logging levels.

Currently we assume that `chalk` always is installed. This has worked
without any issues for a long time because most CLI projects had chalk
installed. This could potentially change in the projects, or the verison of
chalk could accidentally be older/more recent than what our schematics
expect. We just remove colors and depend on the devkit logger for colors
based on specific logging levels.
@devversion devversion requested a review from jelbourn as a code owner November 22, 2019 16:47
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 22, 2019
@devversion devversion added this to the 9.0.0 milestone Nov 22, 2019
@devversion devversion added the P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful label Nov 22, 2019
@devversion
Copy link
Member Author

devversion commented Nov 22, 2019

FWIW: I do not like how we need to pass the logger around.. Also I don't like the type of the logger. logging.LoggerApi is not very intuitive.. Finally, testing with the logger is not as nice as with native console

@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Nov 22, 2019
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

You should file an issue with your feedback

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Nov 22, 2019
@jelbourn jelbourn merged commit e02bb82 into angular:master Nov 22, 2019
@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 Dec 23, 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 P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants