You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the app does not ask for any pickup information. This is a problem because it assumes certain information that may not be correct about the pickup time range and address. While often this information is the default setting, it should be possible to modify it in case of special deliveries. The new plan is to have the conditions be preset with the default settings, and can be clicked through with one button to confirm, or edited.
And since there is limited information for the second page, we can put all this together into one single page
-> the shop coordinate should fill by default the fields
-> the "search for client field" should search in saved adresses, at the endpoint "GET /api/stores/{id}/addresses", the search result should prefill the form
Additional info
POST {{host}}/api/deliveries
{
"store": "/api/stores/1",
"pickup": {
"address": "24, Rue de la Paix",
"before": "tomorrow 13:00",
"comments": "Please call me before pickup"
},
"dropoff": {
"address": "48, Rue de Rivoli",
"before": "tomorrow 13:30",
"packages": [
{"type": "Boxes", "quantity": 2}
],
"weight": 1500,
"comments": "Please call me before delivery"
}
}
The text was updated successfully, but these errors were encountered:
The context
Currently the app does not ask for any pickup information. This is a problem because it assumes certain information that may not be correct about the pickup time range and address. While often this information is the default setting, it should be possible to modify it in case of special deliveries. The new plan is to have the conditions be preset with the default settings, and can be clicked through with one button to confirm, or edited.
Implement changes done for dropoffs:
WITHOUT the packages, tags, or weight fields. This is because the packages and weight and tags should be the sum of the packages tags and weight of the associated dropoffs, so this information is unnecessary.
Dirty Design
And since there is limited information for the second page, we can put all this together into one single page
-> the shop coordinate should fill by default the fields
-> the "search for client field" should search in saved adresses, at the endpoint "GET /api/stores/{id}/addresses", the search result should prefill the form
Additional info
POST {{host}}/api/deliveries
The text was updated successfully, but these errors were encountered: