Skip to content

fix: unable to set display name for collection #2071

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

HarshMN2345
Copy link
Member

Fix: Unable to Set Display Name for Collection (SER-34)

Resolved issues preventing display names from saving in collection settings.

Root Cause

  • Incorrect data sent to API
  • Display names not loaded on init
  • Reactivity issues in Svelte

Fixes

  • Corrected data in setDisplayNames()
  • Loaded saved names on mount
  • Fixed bindings and reactivity

Testing

  • Add, remove, and persist display names
  • Changes persist across sessions

Fixes #2039, resolves SER-34.
WhatsApp Image 2025-07-02 at 17 47 11_b202d694
WhatsApp Image 2025-07-02 at 17 48 02_72f1c462
WhatsApp Image 2025-07-02 at 17 48 38_237073db

@HarshMN2345 HarshMN2345 closed this Jul 8, 2025
@HarshMN2345
Copy link
Member Author

it's already done and this pr is no longer needed

@HarshMN2345 HarshMN2345 deleted the fix-SER-34-Unable-set-display-name-for-collection branch July 8, 2025 09:42
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.

🐛 Bug Report: Unable to set Display Name for Collections
1 participant