For this reason or any other extending circumstance I might want to force Vue to render the vue again. This is where the force update method will come into play as a way to do just that. If I do find myself using it though I cant help but think that I should not be using it, most of the time the reason why a vue is not updating is because an object added to the vue is not reactive, so maybe a better solution would be to make it reactive in that case.
So the force update method should not be a replacement for the Vue.Observable and Vue.set methods.
So lets look at some examples that make use of the force update method, and some others that do the same thing without the use of the method. One situation in which I have found that I need to use the vue force update method is when I have an array of objects that I am not directly rendering in the template, but is used to update a data object value that is used in the template in an updated hook.
Now maybe I should completely change the whole way that I am going about doing this.
yarn global add @vue/[email protected]
For one thing maybe I should update the total value in the tick method rather than in the updated hook.
npm i -g @vue/[email protected]
However this is a post on the force update method so I do have to just come up with a weird situation in which it might need to be used.