Skip to content

Fix get promise never resolving#71

Merged
appy-one merged 1 commit intomasterfrom
fix/handling-server-error-without-cache
Apr 14, 2026
Merged

Fix get promise never resolving#71
appy-one merged 1 commit intomasterfrom
fix/handling-server-error-without-cache

Conversation

@appy-one
Copy link
Copy Markdown
Owner

@appy-one appy-one commented Apr 1, 2026

This fixes a situation where get never yields an error (or result):

  • A value does not exist in cache, and the (resolved) cache promise is handled first
  • The server value can't be loaded because of an error (unauthorized or server error) and the (rejected) server promise is handled second.

* A value does not exist in cache, and the (resolved) cache promise is handled first
* The server value can't be loaded because of an error (unauthorized or server error) and the (rejected) server promise is handled second.
@appy-one appy-one added the bug Something isn't working label Apr 1, 2026 — with GitHub Codespaces
@appy-one appy-one self-assigned this Apr 1, 2026
@appy-one appy-one merged commit d9ad75d into master Apr 14, 2026
1 check passed
@appy-one appy-one deleted the fix/handling-server-error-without-cache branch April 14, 2026 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant