@autobusal/operator-routes 1.5.1 → 1.5.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +13 -0
- package/Locations/Browse/Actions.tsx +24 -6
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,18 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 1.5.2
|
|
4
|
+
|
|
5
|
+
### Removed
|
|
6
|
+
|
|
7
|
+
- **The confirm dialog in front of removing a stop.** It asked the question
|
|
8
|
+
the withdrawal panel already asks - the panel names the stop, lists
|
|
9
|
+
everybody still travelling through it and has its own button - and it
|
|
10
|
+
answered one part wrongly, warning that the fares would have to be entered
|
|
11
|
+
again. That stopped being true when calibration began reconciling price
|
|
12
|
+
rows instead of rebuilding them: measured on a ten-stop route, withdrawing
|
|
13
|
+
a stop keeps fourteen of sixteen fares and drops only the two legs through
|
|
14
|
+
the stop itself.
|
|
15
|
+
|
|
3
16
|
## 1.3.3
|
|
4
17
|
|
|
5
18
|
### Fixed
|
|
@@ -24,11 +24,29 @@ const Actions = ({ item, loading, t, onMove, onDelete }: Props): JSX.Element =>
|
|
|
24
24
|
onMove(order);
|
|
25
25
|
};
|
|
26
26
|
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
27
|
+
/*
|
|
28
|
+
* Edited: Claude - Date: 2026-08-22
|
|
29
|
+
*
|
|
30
|
+
* No window.confirm here any more. Removing a stop opens the withdrawal
|
|
31
|
+
* panel, which names the stop, lists everybody still travelling through
|
|
32
|
+
* it, and has its own explicit button - a far better confirmation than a
|
|
33
|
+
* browser dialog, and the dialog now stood in front of it saying "YOU WILL
|
|
34
|
+
* NEED TO ADD THE PRICES AGAIN", which stopped being true when
|
|
35
|
+
* Locations\Calibration started reconciling price rows instead of
|
|
36
|
+
* rebuilding them. Measured: withdrawing a stop from a ten-stop route kept
|
|
37
|
+
* fourteen of sixteen fares, losing only the two legs through the stop
|
|
38
|
+
* itself.
|
|
39
|
+
*
|
|
40
|
+
* So it was a second gate that asked the same question twice and got the
|
|
41
|
+
* answer wrong once. The panel asks it properly.
|
|
42
|
+
*
|
|
43
|
+
* `locations_manage.actions.delete` is deliberately still in obtapi's
|
|
44
|
+
* language files. obtapi deploys BEFORE the frontends, so for the length
|
|
45
|
+
* of that window the previous bundle is still calling it - and a missing
|
|
46
|
+
* key renders as the key itself, which is what the dialog showed when it
|
|
47
|
+
* was removed. It now says something true and is simply read by nobody
|
|
48
|
+
* once this bundle lands.
|
|
49
|
+
*/
|
|
32
50
|
|
|
33
51
|
return (
|
|
34
52
|
<ContainerActions>
|
|
@@ -80,7 +98,7 @@ const Actions = ({ item, loading, t, onMove, onDelete }: Props): JSX.Element =>
|
|
|
80
98
|
</>
|
|
81
99
|
}
|
|
82
100
|
noMargin
|
|
83
|
-
onClick={
|
|
101
|
+
onClick={ onDelete }
|
|
84
102
|
/>
|
|
85
103
|
</Group>
|
|
86
104
|
</ContainerActions>
|