Feat/recursively get components #60
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
Previously, when we used `self.components,` we only got the top level components because that's what `self.components` holds. Now, we use `self.components` as a starting point and recursively find all child/children components also.
We can now list paths for all exposures that can be obtained from the model declaration. We do not build a simulation of the model, so exposures, connections, and other elements (and so their exposures) that are created at build time are not included.
Add assertions to check for paths for multi-instantiated Population component.
This ensures that later list modifications do not affect stored information.
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.
This improves the exposure path listing functionality to list all paths that can be obtained from the declared model. it traverses the component tree starting at the target node to get all children/instantiations.
Things to check: