-
Notifications
You must be signed in to change notification settings - Fork 245
check: add --format flag, json reporter
#663
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
Draft
adrienthebo
wants to merge
11
commits into
EFForg:main
Choose a base branch
from
adrienthebo:alt/check/json-reporter
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+256
−57
Draft
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
cea78b3
check: add `--report` flag for writing ndjson output
adrienthebo add40da
check: format
adrienthebo 1328f45
check: clean up summarization
adrienthebo 999826f
check: use consistent naming
adrienthebo 73c552e
check: relocate report construction
adrienthebo b881cc5
check: move logging to stderr
adrienthebo b3a2aa7
check: fix lints
adrienthebo ea6e73e
lib: extract DetectionRow out of check
adrienthebo 14d7bee
analyzer: simplify AnalysisRow destructuring
adrienthebo cdd6d9e
check: drop unused imports
adrienthebo b877ce4
check: document log destination reasoning
adrienthebo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you document here why it has to be stderr?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's no longer strictly necessary to log to stderr; my original implementation printed json to stdout for simplicity but since
--pathsupports both files and directories we have to write.ndjsonfiles in order to have a coherent output that matches the daemon ndjson output.My instinct is to revert this change and continue logging to stdout so that
check ... | lesswill work as expected, but I don't have strong feelings either way. I'll document why we made this change if you want to continue with the switch to stderr.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think logging to stderr is still the right thing to do, just asking about documentation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amended in b877ce4.