Fixed 'From Context' blocking thread on resolving data not provided on nearest Context Node#70
Merged
Merged
Conversation
rcosta358
approved these changes
Mar 26, 2026
Comment on lines
+92
to
+94
| val value = current.provided[key] | ||
| if (value != null) { | ||
| return value() as T |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
This PR solves the bug reported in #69 , where the app would block if any node would try to resolve data that wasn't provided in the nearest Context node.
Changes
FromContextnow continues backtracking the tree when no matching key is found. Previously this would iterate over thewhileloop indefinitely.Related Issues
Closes #69
How to Test