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

[BUG] Streamers List does not handle new items being added to the list correctly #99

Open
Brocco opened this issue Apr 28, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@Brocco
Copy link

Brocco commented Apr 28, 2022

Describe the bug
When replaying an event in the dashboard/streamers route, the replayed event is added to the top of the list as it is now the most recent event. If you have an item below expanded, when the list is populated with the new event the item that is expanded is a different item.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'dashboard/streamers'
  2. Click on 'an event under Websocket Stream to expand it'
  3. Click the 'Replay' button
  4. When the list is refreshed notice that a different item in the list is expanded.

Expected behavior
The item that was expanded remains in the expanded state

Screenshots
N/A

Deployment:
Deployment is via railway.
The version is the latest version on main as of Apr 27, 2022.

Additional context
Nope

@Brocco Brocco added the bug Something isn't working label Apr 28, 2022
@Brocco
Copy link
Author

Brocco commented Apr 28, 2022

Theory: Without looking at the code, it appears that the items that are expanded are being tracked based upon an index in an array, and when there is a new item added to the start of the array it now points at the wrong item in the array.

@ched-dev
Copy link
Contributor

ched-dev commented May 6, 2022

I did a little digging and this issue is due to a bug in the PrimeVUE Accordion component when you use :multiple="true" with dynamic tabs. I have opened a bug report with them to fix: primefaces/primevue#2524

Only way for you to fix it for time being would be to manually override with @click actions and manage the active indexes by yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants