Repository navigation
Keep owner wallet access visible at zero balance - #31532
Draft
PavelMurachev wants to merge 1 commit into
Draft
PavelMurachev wants to merge 1 commit into
PavelMurachev wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
The owner's profile currently treats an absent wallet card as zero and hides both. This keeps a valid zero-balance card visible to its owner and provides an entry to the existing wallet window when the public card is absent but the owner's private wallet state is Ready and wallet_available is enabled. Existing cards continue to open the card view; other users' profile behavior is preserved.
The change distinguishes an absent balance from a valid zero. It uses the existing Receive/Add Funds flow and does not add a privacy setting, provision a missing wallet, or override server availability.
Validation: extracted production C++ fragments compiled with GCC 16.2.0, C++20, warnings as errors, Qt Widgets 6.11.2 and pinned rpl libraries. Component checks passed 600 state combinations and 3,320 assertions covering visibility, click routing, account isolation, state changes and subscription teardown. The original-code control fails the owner-zero expectation. Patch applicability and whitespace checks passed. Reproduction, evidence and exact test scope.
Draft for confirmation of the intended owner-only profile behavior. The checks use synthetic session/data/painting adapters; full production translation units and the Telegram application have not been built. Full Debug integration, visual/accessibility review and real-account validation remain pending. The reporter's missing wallet entry has not been reproduced with an identified app version, and may also depend on server provisioning or availability.
The separate API/product proposal covers owner-initiated setup and server-enforced wallet association privacy; those changes are not implemented in this PR.
Platform discussion is published as Telegram suggestion #67181 — Let owners access empty Gram wallets and control wallet visibility in profiles. The card links back to this PR and the API proposal.