Mappedin JS, React & React Native SDK v6.19.0

Features

  • Added includeNonPublic option to getDirections() for routing through navigation nodes that lack the public flag, intended for staff or emergency routing.
const directions = await mapData.getDirections(start, end, {    includeNonPublic: true,});
  • Added interactive option to Image3D.add() so 3D images can receive click and hover events. Interactive Image3D instances are surfaced on a new images field of click and hover event payloads, and the flag can be toggled at runtime via updateState().
const image = mapView.Image3D.add(coordinate, "https://example.com/logo.png", {    width: 2,    height: 1,    interactive: true,});mapView.on("click", (event) => {    if (event.images?.includes(image)) {        mapView.updateState(image, { interactive: false });    }});
  • Added experimental path tracking support to MapView.Navigation via trackCoordinate() with two modes. The tethered mode snaps a tracked coordinate onto the active path and draws a configurable connector when the coordinate strays outside a distance threshold. The travelled mode recolors the portion of the active path the user has already traversed. New isTracking, isShowingOutsideThresholdPath, currentTrackingMode, and travelledFraction getters expose the live tracking state.
mapView.Navigation.trackCoordinate(coordinate, {    mode: "tethered",    tetherThresholdDistance: 10,    outsideThresholdPathStyle: "dashed-boxes",});

Performance

  • Improved footprint rendering performance for floors that do not require ceiling cutouts, resulting in fewer draw calls per frame.

Fixes

  • Fixed an issue where Maker (self-serve) maps loaded via hydrateMapData() were incorrectly identified as enterprise maps, causing authentication errors.
  • Fixed an issue where footprints and ceilings were rendered when multiFloorView.enabled was false but spacesOpenToBelowEnabled was true.
  • Fixed an issue where loading a map without credentials produced spurious “Auth needs to be ready to send analytics” console warnings.
  • Fixed an issue where getScreenCoordinateFromCoordinate() did not account for Coordinate.verticalOffset, causing screen-space projection of elevated coordinates to be misaligned.