Skip to content

[PERTE-333] Use logistics actions on task view #1989

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 81 commits into
base: master
Choose a base branch
from

Conversation

JuanIgAcosta
Copy link
Contributor

@JuanIgAcosta JuanIgAcosta commented May 5, 2025

Issue: #333

Related issue: coopcycle/coopcycle#313
Related PR: #1983


The problem arises because both dispatcher and courier screens/sections uses the same "task detail view".
Starting the task from there, when the backend responds "OK", we update the redux state from courier instead of logistics.

Tasks:

  • Starting the task should update redux state from logistics and/or courier.
  • Review if there is no other remaining action/call with this kind of problem at any other shared component between screens/sections.
  • Make an e2e test for "start task" action, making sure the redux state has the right updated data.

@diegomanuel diegomanuel changed the title Bugfix/333 use logistics actions on task view [PERTE-333] Use logistics actions on task view May 5, 2025
@diegomanuel diegomanuel added bug Dispatch Interface An issue related to dispatch´s interface. Ex: The admin and orders dashboards, using matomo, tags Cooperative: Transversal Concepts labels May 5, 2025
Base automatically changed from feature/313-refactor-modification-of-TaskList-object to master May 9, 2025 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Cooperative: Transversal Concepts Dispatch Interface An issue related to dispatch´s interface. Ex: The admin and orders dashboards, using matomo, tags
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants