Repository navigation
Conversation
✅ Deploy Preview for footballplayer-online ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Selecting a theme previously announced success before persistence finished, then stacked an error when saving failed. Persistence also failed before the RPC: the raw Supabase Auth identity has role authenticated and no workspace billing context, so the existing staff mutation guard rejected it with payment_required.
This web-only fix supplies the matching loaded account profile to the unchanged billing/demo guard, retains the JWT-authorised self-service RPC, waits for persistence before success, replaces previous theme notices, serialises/coalesces rapid changes and suppresses stale responses after another selection, account switch, logout or unmount. Missing/mismatched profiles, unknown roles, unpaid paid-plan staff, demo identities and server authority denials remain blocked. System/Light/Dark defaults and branding remain compatible.
Current main b40b593 (approved PR163 tooling repair) is merged into this feature branch. Final head: d0cac3c. Other feature branches were not absorbed. The feature diff is eight files: UserSettingsPage, core theme persistence, Toast provider, latest-theme-save controller, three theme regression files and two additive CI lines. It adds no dependency, migration, native or permission change.
Validation at final head:
The previous two required security failures are resolved by integrating approved PR163; no check was weakened. A fresh local dependency reinstall hit ENOSPC, and only this task's incomplete install was removed before restoring its original dependency junction. Exact-head CI clean installs and all required gates succeeded. Other worktrees and pending cleanup archives were untouched.
Earlier exploratory tests/*.test.mjs results showed 84 identical failures on the pre-tooling main and initial candidate, with no introduced failures. That collection and test:platform are not configured release gates; they were not substituted for the seven exact-head checks above.
Report: https://app.slack.com/archives/C0C5N2XEQHM/p1790924386964299 . Parent inspected the original screenshot and confirmed both notices. Local reproduction proves the pre-RPC rejection; no separate live server error was attributed without a request trace.
Rollback, if later required: revert this feature through the reviewed Git/build pipeline to the b40b593 source while retaining PR163. The combined reverse patch checks cleanly. No database or native rollback is required; stored theme values remain compatible.
Draft only. Await separate parent release direction. Independent mobile security review remains outside this web change. No feature merge, production deployment, migration, OTA, live account mutation or customer communication was performed.