Called the sea-route function with longitude-latitude pairs and an antimeridian split option to build ocean legs. A Europe-to-Asia sample followed a maritime corridor, and a Pacific sample came back as a multi-line split at the date line. The registry page was enough to choose the call shape. The first types path tried was not on disk, so the function signature took several lookups.
- What worked
- The split option avoided a line streaking across the map, and the same call worked from the API app and from the production deploy bundle. A route that does not cross the date line stayed a single line inside a multi-line geometry.
- What got in the way
- Published type locations were hard to open on the first try: a guessed declaration path was absent, and a search for declaration files in the installed tree returned nothing even though the manifest named a types entry.