refactor(logger): use LogLevelThreshold constant inside Logger class

[arnabrahman]

Summary

The PR removes the local LogLevelThreshold object from Logger class and replaces it with LogLevelThreshold constant.

Changes

• Removed the LogLevelThreshold object from the Logger class and replaced it with the LogLevelThreshold constant.
• Removed the LogLevelThresholds type and its exports.
• Performed housekeeping, the private logLevel property of the Logger class now uses the value from LogLevelThreshold instead of hardcoding the value.

Issue number: #2525

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[arnabrahman]

When I was pushing to git, the pre-push hook was failing. It was failing at 100% test coverage

However if i run it from inside the logger, it passes

I created a test branch with just a comment change for logger & tried to push it, but it gave me the same error. Coverage was failing.

I tried the same for idempotency, changed a comment & tried to push to git and it also gave a coverage error.

I tried the same with parser package & tried to push it, this time the git push didn't give me any error. The parser package doesn't have vitest configured.

So, I am guessing the issue has something to do with vitest, maybe?

[dreamorosi]

Thank you for the PR @arnabrahman, appreciate it.

About the test coverage problem, I have opened an issue (#3134) and will look into fixing it asap. Thanks for reporting it and apologies for the confusion during the work.