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

[WNMGDS-346] Use console warn and remove logs from production #596

Merged
merged 3 commits into from
Jan 13, 2020

Conversation

bernardwang
Copy link
Contributor

Changed

  • Removes console.error in favor of warn
  • Scopes logs to development and test envs only

@bernardwang
Copy link
Contributor Author

Closes #595

Copy link
Contributor

@line47 line47 left a comment

Choose a reason for hiding this comment

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

I'm wondering if we should make mention of this under deprecation on the component maturity page? https://design.cms.gov/guidelines/component-maturity/

Saying something like deprecation warnings are warning-level and are only visible in development

@bernardwang
Copy link
Contributor Author

We could add that, but I also think that most people assume a dependency shouldn't be logging out dev related warnings in production. TBH I feel like this is mainly an oversight on our part

@bernardwang
Copy link
Contributor Author

Also, this needs to wait for this PR to merge
#593

@bernardwang bernardwang merged commit f009b2e into master Jan 13, 2020
@bernardwang bernardwang deleted the WNMGDS-346/scope-console-msgs branch January 13, 2020 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants