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

Update node record after updating #929

Merged
merged 3 commits into from
Jan 19, 2025
Merged

Update node record after updating #929

merged 3 commits into from
Jan 19, 2025

Conversation

Boy132
Copy link
Member

@Boy132 Boy132 commented Jan 18, 2025

Fixes #926

@Boy132 Boy132 self-assigned this Jan 18, 2025
@RMartinOscar
Copy link
Contributor

RMartinOscar commented Jan 18, 2025

Doesn't fix the issue i still have to refresh the page to see correct data
BTW why do we replicate the Model ?

@Boy132 Boy132 requested a review from RMartinOscar January 19, 2025 00:25
@Boy132 Boy132 changed the title Refresh node model after updating Update node record after updating Jan 19, 2025
@Boy132 Boy132 merged commit 9e8b9cd into main Jan 19, 2025
17 checks passed
@Boy132 Boy132 deleted the boy132/refresh-model branch January 19, 2025 00:28
@github-actions github-actions bot locked and limited conversation to collaborators Jan 19, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Node values revert to original after saving, requiring a page reload to update properly
2 participants