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

refactor, reduce the usage of legacy scope/comp for snapping API #9437

Merged
merged 2 commits into from
Jan 10, 2025

Conversation

davidfirst
Copy link
Member

Improve the Snapping API by changing from ConsumerComponent to Component and prefer using Scope over LegacyScope when working with Remotes.

@davidfirst davidfirst enabled auto-merge (squash) January 10, 2025 15:57
@davidfirst davidfirst merged commit 383539d into master Jan 10, 2025
10 checks passed
@davidfirst davidfirst deleted the refactor-snapping-sign branch January 10, 2025 16:59
davidfirst added a commit that referenced this pull request Jan 17, 2025
In some cases, when tagging or snapping with `--build` flag, the
buildStatus remain `pending`, instead of `succeed`.
This is a regression caused by #9437.
It happens for example when tagging/snapping aspects.
It's happening because the `ConsumerComponent instance inside the
harmony component is different than the one originally created. Although
the harmony component is created by the legacy, but in case the
`Workspace` aspect already had this component in the cache, it won't use
the provided legacy, but create a new one.
As a result, the buildStatus was set to one instance of
ConsumerComponent and another instance was saved into the filesystem.

This PR fixes it by making sure it's using the same instance of
`ConsumerComponent`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants