Skip to content

Conversation

@Schlauer-Hax
Copy link
Member

No description provided.

…n panel

When updating wallet fields (accountType, cut, copyrightEditable),
the transactions were disappearing from the frontend UI even though
they remained in the backend database.

The issue was that after updating a field, the wallet refresh call
would sometimes receive a response without transactions included.
This caused the frontend wallet state to lose transaction data.

Solution: Preserve the current transactions before the update, and
restore them if the refreshed wallet data doesn't include them.
This ensures transactions are never lost in the frontend UI,
regardless of what the backend GET response contains.
Extended the fix to preserve not just transactions, but also cut and
balance fields when updating wallet properties via the admin panel.

When updating wallet fields (accountType, cut, copyrightEditable),
the backend GET response sometimes doesn't include all fields,
causing them to disappear from the frontend UI.

Now preserving:
- transactions (transaction history)
- cut (user's cut percentage)
- balance (wallet balance object)

This ensures all critical data remains visible in the UI regardless
of what the backend refresh response contains.
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.

3 participants