feat(main): update PARSER_VERBOSE handling to check for non-zero inte… #25
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes updates to the handling of the
PARSER_VERBOSEenvironment variable in both the documentation and the source code. The changes ensure that the variable must be set to a non-zero integer value to enable verbose logging.Changes to documentation:
readme.md: Updated the description of thePARSER_VERBOSEenvironment variable to specify that it must be set to a non-zero integer value to enable verbose logging.Changes to source code:
src/main.c: Modified the code to check if thePARSER_VERBOSEenvironment variable is set to a non-zero integer value before setting the log level to verbose.