@autobusal/order-confirm 1.3.0 → 1.3.1
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/OrderConfirm.tsx +10 -1
- package/package.json +1 -1
package/OrderConfirm.tsx
CHANGED
|
@@ -120,7 +120,16 @@ const OrderConfirm = ({ t }: Props): (JSX.Element | null) => {
|
|
|
120
120
|
return <Navigate to="/" />;
|
|
121
121
|
}
|
|
122
122
|
|
|
123
|
-
|
|
123
|
+
/*
|
|
124
|
+
* Claude - 2026-09-07, for Ferjolt: "When I click try again, appears
|
|
125
|
+
* /viewtrip/ while the 'Order Number' field is autofilled with
|
|
126
|
+
* 2w7p1v915xm4gln instead of MSR4YD". The lookup accepts either, but the
|
|
127
|
+
* field is labelled Order Number and this page already knows the real
|
|
128
|
+
* one (it is the one printed in the sentence above the buttons), so that
|
|
129
|
+
* is what the link carries - falling back to the hash only while the
|
|
130
|
+
* number is still loading.
|
|
131
|
+
*/
|
|
132
|
+
const destination = UserData ? '/account/orders' : `/viewtrip/${ orderNumber || hash }`;
|
|
124
133
|
|
|
125
134
|
const onManage = (): void => {
|
|
126
135
|
// a logged-in user shouldn't be sent to the public order-lookup form (which
|