-
-
- {kind ? : }
-
-
-
{draft.poi.name}
-
- {t('roadtrip.stop.landsOn', { day: draft.dayNumber, position: draft.position + 1 })}
-
-
-
-
- {duplicateName ? (
- // The full place form warns about duplicates; losing that warning would make
- // this the easiest way to add the same petrol station twice.
-
-
- {t('roadtrip.stop.duplicate', { name: duplicateName })}
-
- ) : null}
-
- {/* Only where sleeping is on the table. A petrol station gets no choice, because
- there is nothing to choose between. */}
- {overnight && onSaveNight ? (
-
- {[
- { on: false, label: t('roadtrip.stay.mode.pause'), Icon: Hourglass },
- { on: true, label: t('roadtrip.stay.mode.night'), Icon: BedDouble },
- ].map(({ on, label, Icon }) => (
-
- ))}
-
- ) : null}
-
- {asNight ? (
-
- {/* Check-in only, and optional at that: it is the hour the drive can stop
- for the night, which is the one thing about a booking the chain uses.
- A check-out says when the room has to be back, never when anybody sets
- off, so it is a booking detail and lives under Days with the rest of
- them. A hotel found on a map has no idea when its reception opens. */}
-
- {websiteHref || draft.poi.phone ? (
-
- ) : null}
-
- ) : (
- <>
-
-
- {t('roadtrip.stop.kind')}
-
-
-
-
-
-
- {t('roadtrip.stop.stay')}
-
-
-
-
- {/* How busy the charging area is and what it charges, while the stop is still
- being considered rather than once it is on the trip. Only for the kind that
- has an answer: a petrol station or a bakery asks nothing, so picking either
- of those costs no request at all.
-
- One panel for one station, for as long as the dialog is open. The corridor
- list deliberately does not do this per row: it publishes results box by
- box, each row would own its own refresh timer, and a station in a dense
- row of chargers is the case the upstream match refuses as ambiguous. */}
- {stopType === 'charging' ? (
-
-
- {t('roadtrip.charging.availability')}
-
-
-
-
-
- ) : null}
- >
- )}
-
-