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

[core] Investigate if warnings.warn calls can be replaced with INFO level logging #270

Open
t1m0thyj opened this issue May 29, 2024 · 2 comments
Labels
bug Something isn't working priority-low severity-low
Milestone

Comments

@t1m0thyj
Copy link
Member

Now that we have logging in place, we might be able to remove the suppress_config_file_warnings flag and log some of the config file warnings at INFO level instead.

However I think that removing warnings that were already present would be outside the scope of the effort to add a logger, so this could be addressed in a separate issue 🙂

Originally posted by @t1m0thyj in #268 (comment)

@github-project-automation github-project-automation bot moved this to New Issues in Zowe CLI Squad May 29, 2024
@zFernand0 zFernand0 added this to the v1 LTS milestone Jun 11, 2024
@zFernand0 zFernand0 added bug Something isn't working Research Needed labels Jun 25, 2024
Copy link

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

@zFernand0
Copy link
Member

Only print warning is the user needs to take action. Log otherwise.

@zowe-robot zowe-robot moved this from New Issues to Low Priority in Zowe CLI Squad Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-low severity-low
Projects
Status: Low Priority
Development

No branches or pull requests

2 participants