add json output #102
Merged
add json output #102
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
Closed
nineinchnick
force-pushed
the
json
branch
8 times, most recently
from
6f45f50
to
64443ba
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.
Allow dumping whole model with findings into a json file. To make the schema a bit more sane some refactor was required, like:
_BagOfprefixesAssetclass used between Element and assets like Server, Datastore, etc - this was required so that Boundary can still inherit from Element but without unused attributes. This also allowed moving more common attributes down to the base class. It also helps separate some attributes from Dataflow and base class.The JSON file is somehow denormalized.