Add option to parse all JSON files #47
Merged
Conversation
This file contains 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
|
@aras-p Could we please get this change into the mainline branch? |
ArekSredzki
reviewed
Jul 23, 2020
ArekSredzki
reviewed
Jul 23, 2020
Co-authored-by: Arek Sredzki <arek@sredzki.com>
Co-authored-by: Arek Sredzki <arek@sredzki.com>
This was referenced Oct 3, 2020
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.
The
--start/--stopprotocol is convenient to analyze incremental builds, but it's somewhat cumbersome to analyze from-scratch builds, especially if we want to zoom in on specific directories.This commit adds an option
--allthat works like--stopexcept it doesn't need a--start, it will just analyze all the found JSON files.