feat: dep-graph json output file #5619
Draft
+47
−0
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
gitphill
force-pushed
the
feat/dep-graph-json-output-file
branch
from
d840e98 to
704e838
Compare
When both `--print-deps` and `--json-file-output` are being used produce a depGraph object in the resulting JSON file. Does not attempt to fix any existing `--json` output formats to reduce the potential of breaking changes. This allows CLI users to see the dependency graph that was resolved by the plugin code and scanned.
gitphill
force-pushed
the
feat/dep-graph-json-output-file
branch
from
704e838 to
1cf2540
Compare
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.
Pull Request Submission Checklist
What does this PR do?
When both
--print-depsand--json-file-outputare being used produce a depGraph object in the resulting JSON file.Does not attempt to fix any existing
--jsonoutput formats to reduce the potential of breaking changes.This allows CLI users to see the dependency graph that was resolved by the plugin code and scanned.
Where should the reviewer start?
How should this be manually tested?