refactor(scanner,model): Move NestedProvenance to model #8724
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.
Moving the
NestedProvenance
data structure to model, allows it to be used within the model without creating a circular dependency between scanner and model.This would enable a future
AnalayzerInput
class [1] to utilize it and still be placed into the model,where its predecessor
Repostory
is already located.[1] #2896 (comment)
Signed-off-by: Jens Keim jens.keim@forvia.com