When clicking on “Edit” for an article, the meta AND content should be the ones fetched from the API.
What happens
The article content in the UserInput component is the one from one step behind, suggesting that the Vuex state is not updated properly.
#What's expected to happen
When clicking on "Edit" for an article, the meta AND content should be the ones fetched from the API.
#What happens
The article content in the `UserInput` component is the one from one step behind, suggesting that the Vuex state is not updated properly.
Possible explanation : the component is mounted before the Vuex mutation.
Hence the following behavior :
the user clicks on “edit”
the mutation is commited by the EditPage component
the UserInputPage component is loaded, with the unmutated state
the mutation is achieved, but not taken into account by the UserInputPage component.
Solution : await the mutation before calling router.push()
**Possible explanation** : the component is _mounted_ before the Vuex mutation.
Hence the following behavior :
1. the user clicks on "edit"
2. the mutation is commited by the `EditPage` component
3. the `UserInputPage` component is loaded, with the unmutated state
4. the mutation is achieved, but not taken into account by the UserInputPage component.
**Solution** : `await` the mutation before calling `router.push()`
What’s expected to happen
When clicking on “Edit” for an article, the meta AND content should be the ones fetched from the API.
What happens
The article content in the
UserInput
component is the one from one step behind, suggesting that the Vuex state is not updated properly.Possible explanation : the component is mounted before the Vuex mutation.
Hence the following behavior :
EditPage
componentUserInputPage
component is loaded, with the unmutated stateSolution :
await
the mutation before callingrouter.push()