Skip to content

fix: tie key checks to the request that started them - #93

Merged
ykisana merged 1 commit into
mainfrom
key-check-request-scope
Nov 12, 2026
Merged

ykisana merged 1 commit into
mainfrom
key-check-request-scope

Conversation

@ykisana

@ykisana ykisana commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Widget links that arrive while a key check is open could reuse it for a different action, e.g. "Block Without Key" running an unlock, or the duration sheet switching groups.

Key checks now belong to the request that opened them and restart when a newer one arrives. QR scans only complete the scan they validated.

Part 1 of splitting up the Shortcuts unblock work.

A widget link that arrived while a key check was open could reuse that
screen for a different action: Block Without Key could run the unlock, and
the duration or location sheet could switch to another group. Each check
now belongs to the request that opened it and restarts when a newer one
arrives, and QR scans only complete the scan they validated.
@ykisana
ykisana merged commit d8247e2 into main Nov 12, 2026
2 checks passed
@ykisana
ykisana deleted the key-check-request-scope branch November 12, 2026 23:50
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