Skip to content

Add direct result consumption - #2

Merged
eosobande merged 1 commit into
mainfrom
feat/direct-consumption
Aug 12, 2026
Merged

Add direct result consumption#2
eosobande merged 1 commit into
mainfrom
feat/direct-consumption

Conversation

@eosobande

@eosobande eosobande commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add direct consume-once access through ResultConsumer.consume(key).
  • Add PendingResult.Missing and PendingResult.Value.
  • Keep the callback-based consumption API.
  • Distinguish a missing result from PendingResult.Value(null).
  • Update the public API declarations and documentation.
  • Add the 0.2.0 changelog entry.

Usage

when (val result = resultConsumer.consume(resultKey)) {
    PendingResult.Missing -> Unit
    is PendingResult.Value -> handleResult(result.value)
}

The result remains consume-once. The first direct or callback consumer removes it from the store.

Validation

  • Android unit tests passed.
  • iOS simulator tests passed.
  • API compatibility checks passed.
  • Kover line and branch coverage checks passed at 100%.
  • The full check, apiCheck, and koverVerify tasks passed.
  • Sample tests and Android assembly passed.

Review

RECOMMEND_ACCEPT


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@eosobande eosobande self-assigned this Aug 12, 2026
@eosobande
eosobande merged commit 52330b4 into main Aug 12, 2026
3 checks passed
@eosobande
eosobande deleted the feat/direct-consumption branch August 12, 2026 08:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant