Repository navigation
fix(mobile): new-task context no longer changes every render - #22134
Merged
maria-rcks merged 9 commits intoOct 30, 2026
Merged
Conversation
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.
Note
Written by
gpt-6.1-solon behalf of MariaProblem
on mobile, the new-task provider and paginated branch hook lost compiler caches, causing unchanged renders to return new values and rerender consumers.
Change
moves sticky-model and model-clock subscriptions before model derivation, and host-environment derivation after the last hook, so the compiler retains those caches. two local
useMemocalls keep branch page atoms stable while preserving live updates, pagination, refresh, and target changes. the scheduled-task branch picker uses the same hook.keeps flamboh's original commits and the prior takeover fixes. merges current main (
812c0a71c785) without rewriting history, preserving main's project-defaults flow. the diff remains four files.Scope and approval
this is a focused fix for an existing cache invalidation bug, qualifying for the obvious-bug exemption in CONTRIBUTING.md. it restores stable values across unchanged renders without adding capabilities or changing defaults. both provider ordering and branch atom stability are needed to prevent new-task context churn.
Verification
verification at
510f5894e71c69443ad9e4d742d9aa2ff07d0fda:vp run check:changedpassed through blacksmith: formatting, lint, both knip passes, mobile/scripts typechecks, and 1,008 tests in four files.useMemoimport after the merge.originally also covers the branch-hook issue described in https://git.cafe/pingdotgg/t3code/pulls/22132.
gpt-6.1-sol via the codex harness in t3 code.