Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix: Restore geometries too #5108

Merged
merged 1 commit into from
Dec 11, 2024
Merged

Conversation

vbustamante
Copy link
Contributor

Signed-off-by: Victor Bustamante <victor@systeminit.com>
@britmyerss
Copy link
Contributor

Looks good to me - but we should either add a new test or expand an existing one to cover this going forward.

@@ -3332,6 +3332,10 @@ impl Component {
ctx.add_dependent_values_and_enqueue(component.input_socket_attribute_values(ctx).await?)
.await?;

Geometry::restore_all_for_component_id(ctx, component_id)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason you went here vs. expanding the import_component_subgraph is because the geometries aren't in the subgraph of the component?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@britmyerss yeah, the subgraph code is very generic. Since we've structured our geometries the other way around I had to implement a special case here

@vbustamante vbustamante added this pull request to the merge queue Dec 11, 2024
Merged via the queue into main with commit f6370ac Dec 11, 2024
8 checks passed
@vbustamante vbustamante deleted the victor/restore-geometries-too branch December 11, 2024 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants