Skip to content

improvement(watch), enable triggering onComponentChange on another component #9301

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

Merged
merged 2 commits into from
Nov 13, 2024

Conversation

davidfirst
Copy link
Member

Introduced a new flag --trigger <component-id>, when any change is happening, it runs the workspace.onComponentChange for the specified component-id.
A real use case when this is needed is developing a vscode extension component. Because a vscode-extension must be bundled, its dependencies are always in the dist of the extension. As a result, when a dependency in the workspace is changed, the extension is not aware of it and not getting updated.
This flag is more like a workaround and not the best solution. Ideally, the flag would be "trigger-dependents" which would traverse the graph and trigger accordingly, but it's not worth it to implement as this point as it's an edge use-case.

@davidfirst davidfirst merged commit 0dfbcee into master Nov 13, 2024
11 checks passed
@davidfirst davidfirst deleted the watch-trigger-dependent branch November 13, 2024 17:40
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