This depends on more personal approach, I think. I personally think that making any queries at all is not necessary, if we certainly know what kind of change has been made. Or we can query for that specific object only, not the entire list. Or our API can be configured in a way that it returns the new, updated object from the database if the edit was successful (that's my favorite).
But one may argue that refreshing the entire list is a bad idea. It is
- A heavier query for the database
- More items to convert to JSON in backend
- More data sent through network
- More JSON to parse in frontend
As you see, this is cumbersome, and if you have many users, they may start bombarding the database with queries, though each knows (speculatively somewhat, but mostly correctly) how there data does look like at the very moment. So if the API cannot be configured to return the updated object, I suggest either to query only for the updated object, or not querying at all -- if we know what changes we requested the backend to make in the database, and we know the backend succeeded in doing that, then we just apply the changes in our frontend without any further thought