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

fix: duplicate record display on rapid consecutive refreshes #360

Merged
merged 2 commits into from
May 12, 2024

Conversation

szktkfm
Copy link
Contributor

@szktkfm szktkfm commented May 5, 2024

Summary

This PR addresses #294

I have implemented a modification to retain the TaskID for each fetch task within the model. This TaskID is identical to the one included in the msg sent upon the completion of a record fetch. Saving taskID within the model is a Last-Write-Wins basis, ensuring that only the most recent TaskID is stored in the model.

The PR and issue lists within the model are updated only if the TaskID in the model matches the TaskID in the incoming message.

How did you test this change?

I manually tested this change following the procedures shown in the video below. I confirmed that the issue was resolved without negatively impacting other functionalities such as paging or searching.

Images/Videos

gh-dash-pr02.mp4

Copy link
Owner

@dlvhdr dlvhdr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! This is great!
Sorry for the delay :/ Just had a minor comment

ui/components/section/section.go Outdated Show resolved Hide resolved
@dlvhdr dlvhdr merged commit 6f57521 into dlvhdr:main May 12, 2024
2 checks passed
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.

2 participants