Skip to content
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

FE: Topics: Save field previews into local storage #439

Open
Haarolean opened this issue Jun 12, 2024 · 0 comments · May be fixed by #449
Open

FE: Topics: Save field previews into local storage #439

Haarolean opened this issue Jun 12, 2024 · 0 comments · May be fixed by #449
Assignees
Labels
area/messages area/topics scope/frontend Related to frontend changes status/triage/completed Automatic triage completed type/enhancement En enhancement/improvement to an already existing feature

Comments

@Haarolean
Copy link
Member

Topic field previews should be saved per topic per user in local storage.

Expected:

  1. Add a topic field preview ("preview" button/link near "key" and "value" tabs in topic messages view)
  2. Refresh the page
  3. Field previews are still present

Actual:
3. Field previews are gone

@Haarolean Haarolean added type/enhancement En enhancement/improvement to an already existing feature scope/frontend Related to frontend changes area/topics area/messages labels Jun 12, 2024
@kapybro kapybro bot added status/triage Issues pending maintainers triage status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Jun 12, 2024
Nilumilak added a commit that referenced this issue Jun 20, 2024
@Nilumilak Nilumilak linked a pull request Jun 20, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/messages area/topics scope/frontend Related to frontend changes status/triage/completed Automatic triage completed type/enhancement En enhancement/improvement to an already existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants