fix: refresh profile after email verification - #27
Open
bluewandd wants to merge 1 commit into
Open
Conversation
Author
|
Superseded. This PR has been rewritten as a single independent change against current The earlier branch was based on |
This was referenced Sep 2, 2026
bluewandd
force-pushed
the
pr/lepse-email-verification
branch
from
September 6, 2026 07:34
260fe99 to
5a576a7
Compare
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
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.
An already-open Lachesis window could keep showing the email-verification banner after verification completed elsewhere. The server updated the profile, but the cached response was not refreshed on window activation.
The profile query now refreshes on visibility or window focus only while its cached profile is not verified. Once verification succeeds, later focus returns generate no profile requests. Startup uses the canonical profile key and skips profile requests when there is no session, avoiding the previous anonymous request and refreshing persisted profile data with one request.
The token checks are request guards only; they are not cache isolation and this change does not claim to clear or hide hydrated data. Ordinary query defaults remain unchanged.
A focused Query harness confirmed the normal false/true states, malformed cached data, request counts, and absence of unhandled rejections. Formatting and diff checks pass.