Sounds like an unpolished async change - it changes only after the server has confirmed successfully saving. I often hit this in my projects and if I want to be safe I would usually add a progress to make sure the user knows what's happening, but when it's not a critical change (losing a new name of a column would classify for that in my book) I would just apply the new state on the client for better UX, risking losing the change if the user somehow navigates away/kill the app before a request is sent/completed. It's just better UX, IMO.
No comments yet.