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

Implement Data Refresh Mechanism in Next.js Application to Reflect Underlying Data Changes #1201

Open
Musyonchez opened this issue Mar 27, 2024 · 2 comments

Comments

@Musyonchez
Copy link
Contributor

Currently, your Next.js application does not automatically refresh or re-render components when the underlying data changes. This can lead to a situation where the data displayed in the UI is outdated and does not reflect the current state of the data source.

This issue can be misleading for users, as they may be making decisions or taking actions based on outdated information. It can also lead to inconsistencies between different users' views of the data if they are accessing it at different times.

I propose that you implement a mechanism to refresh the data or re-render the affected components when changes to the underlying data occur. This could involve using a state management library, implementing a polling mechanism, or using websockets for real-time updates, depending on your application's needs and the nature of the data changes.

By implementing this change, you can ensure that the users UI always reflects the most current state of the data, leading to a more accurate and user-friendly application.

@niwsa
Copy link
Member

niwsa commented Mar 28, 2024

@Musyonchez Thank you for reporting. Where exactly do you see this issue ?

@Musyonchez
Copy link
Contributor Author

Like in some pages where the user performs an action like submit the underlining data may change such that the data the user is viewing on their screen is like old data and if someone does not understand that nextjs does not rerender its page may rerun an action without knowing it worked. Or have like success messages for every action to show it was done.

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

No branches or pull requests

2 participants