extract and isolate error handling from GitStore internals #6613
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.
Overview
First part of #6595
Currently the default error handling has been owned by
GitStore
, but as we've moved towards running Git operations outside of aGitStore
(because we don't need to cache the result), there has been some confusion about the right way to leverage the inbuilt error handling so that unhandled errors do not bring down the app.Description
This PR extracts the logic for
GitStore.createFailableOperationHandler
into it's own module, and provides a more familiarwithErrorHandling
function in the places where this is currently used.Release notes
Notes: no-notes