Skip to content

Change set level to allow for all possible verbosity levels to be set #10

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.

Sign up for GitHub

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

Jump to bottom
Merged
peterbppb merged 1 commit into from
Mar 28, 2024
Merged

Change set level to allow for all possible verbosity levels to be set #10

peterbppb merged 1 commit into from
Mar 28, 2024

Conversation

@peterbppb
Copy link
Contributor

@peterbppb peterbppb commented Mar 26, 2024

Currently we can only set the verbosity level to

  • ERROR
  • max between effective level and INFO
  • DEBUG
  • DEBUG

I think it should be possible to enforce the INFO level or the WARNING level if we wish to do that

@peterbppb peterbppb requested a review from a team as a code owner March 26, 2024 09:55
@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 26, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@peterbppb peterbppb merged commit c2acbd0 into develop Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@DDuarte DDuarte DDuarte approved these changes

@fpintoppb fpintoppb Awaiting requested review from fpintoppb fpintoppb is a code owner automatically assigned from surface-security/core

@lemosd-ppb lemosd-ppb Awaiting requested review from lemosd-ppb lemosd-ppb is a code owner automatically assigned from surface-security/core

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@peterbppb @DDuarte