You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The changes introduced in #440 made stuff much faster, that's great!
However, when changing a rental status, the changes only appear in the paginated TableView after reloading the tab/page. Would it be possible to force a reload/reindexing after saving/chaning a doc?
See here for example
The text was updated successfully, but these errors were encountered:
Hm, I cannot reproduce this issue. Which browser and which version of the code did you use? Looks like the 111-complete-return-button branch? Were there any errors in the browser console?
a refresh only occurs if something actually changes
a refresh also occurs if something was changed by another device
My best guess is that this change listener does not always work. We could investigate that by adding some logging to the change listener.
Or we could simplify this whole refresh logic by only refreshing when the user clicks "Speichern". However, then we would not refresh when something was changed on another device. I think this might be a good solution? What do you think?
The changes introduced in #440 made stuff much faster, that's great!
However, when changing a rental status, the changes only appear in the paginated
TableView
after reloading the tab/page. Would it be possible to force a reload/reindexing after saving/chaning a doc?See here for example
The text was updated successfully, but these errors were encountered: