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.

Sign up for GitHub

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

Jump to bottom

Forms don't update updatedAt and other fields after background fetch or mutation #160

Closed
neopostmodern opened this issue Aug 7, 2022 · 1 comment
Closed

Forms don't update updatedAt and other fields after background fetch or mutation #160

neopostmodern opened this issue Aug 7, 2022 · 1 comment
Labels
bug critical regression
Milestone
v0.20.2

Comments

@neopostmodern
Copy link
Owner

In combination with b1cd50c (fix for #155) this prevents any subsequent save to a first save (because updatedAt increases server-side but is not reflected in the form data) or any save at all if there is a stale updatedAt in cache (until a reload to get the [updated] cache into the form).
@neopostmodern neopostmodern added this to the v0.20.2 milestone Aug 7, 2022
@neopostmodern
Copy link
Owner Author

Regression from b1cd50c, does not affect 0.20.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug critical regression
Projects
None yet
Milestone
v0.20.2
Development

No branches or pull requests
1 participant
@neopostmodern