Fix incorrect error handling in template-fetcher service #801
Conversation
This file contains 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
elpoelma
force-pushed
the
fix/template-fetcher-error-handling
branch
from
3b38207 to
02e6905
Compare
piemonkey
approved these changes
Jan 6, 2025
I also managed to miss it in reviewing 😬 |
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.
Overview
This PR solves an issue introduced in #797
The
!response.okcondition used in thetemplate-fetchershould beresponse.ok.connected issues and PRs:
None
Setup
None
How to test/reproduce
Ensure you can correctly fetch + instantiate templates coming from RB.
Checks PR readiness