refactor: bubble init usage and errors to simplify recovery #221
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.
Checklist before requesting a review
Type of change
Please delete options that are not relevant.
Describe your changes
Need to refactor how
initialize()
is used so that is bubbles errors instead of just logging them. This way we can use the actual error reasons fornotify
or when user invokes API to show reasons for component not being able to recover. Needs work:initAndLog
as convenience methodforce
init when things aren't working as planned and user wants to force a full recoverynotify
usage to pull error causes and consolidate where these happentestAuth
to try-catchError
classes for init steps to make extracting the desired errorcause
easier?poll
endpoints so allow re-initializing non-polling components as wellIssue number and link, if applicable
#220