Simplify loading and saving of stacks in handlers #386
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
geofflamrock
force-pushed
the
improve-stack-loading-and-saving
branch
from
0a09387 to
99a6ab5
Compare
geofflamrock
changed the title
geofflamrock
changed the title
geofflamrock
force-pushed
the
improve-stack-loading-and-saving
branch
from
91f2125 to
ab1410e
Compare
This was referenced Oct 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently there is a lot of repeated code when loading stacks, checking that we only operate on stacks for the current remote uri.
Replaces this with a
IStackRepositoryinterface and implementation which filters to only stacks for the current remote to clean up a bunch of internal handler code.