#1 Article content is one step behind

Closed
opened 4 months ago by theolem · 1 comments
theolem commented 4 months ago

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.

#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.
theolem commented 4 months ago
Owner

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()

**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()`
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
Cancel
Save
There is no content yet.