fix(IFC): Fixed duplicate elements #604
Merged
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.
Previously, we were selecting all spatial children to as
RootIds
to become immediate children of the rootCollection
speckle object. Additionally they were also included during traversal as spatial children to be nested under the "elements" property during recursive traversal.Obviously these two strategies cannot both be employed without leading to the problem in question where many copies of each element was included in the tree.
(i.e. all spatial relationships were being sent flat AND included as nested children via the traversal)
See Linear ticket for an example Speckle model
Pre PR (slightly simplified)
Post PR