fix: always clean up pre events W-20002028
#828
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.
What does this PR do?
While working on supporting
ignoreConflictsin the deploy/retrieve tools for the dx mcp here we found some issues:salesforcecli/mcp#321
Unlike CLI, the mcp is a long running process and a new
SourceTrackinginstance gets created on each tool call.STL handles events by attaching listeners to a global singleton (sfdx-core's
Lifecycle), in an mcp process all deploy/retrieve tool calls would listen to the events (or not) depending on if the first call did setignoreConflicts.We now clean the pre events inside
maybeSubscribeLifecycleEvents(always called when instantiatingSourceTracking) so ensure each instance is clean.Each instance can subscribe to the pre events by setting
ignoreConflicts.What issues does this PR fix or reference?
@W-20002028@