Repository navigation
Extend JourneyMap appearance, selection and moving markers - #60
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
JourneyMap now supports theme-aware label halos, marker sizing and colors, partial base-map palettes, independent multi-selection and smooth moving markers. Following marker content can use custom React nodes with four-way placement and spacing. Stable marker IDs preserve camera and native marker instances during updates.
Tabs can collapse icon-backed labels when space is insufficient, retaining accessible names, focus, keyboard navigation and tooltips. The merge preserves current main’s map lifecycle, full-height sizing and late-callback protections.
Validation
Node 24.22.1 / React 19.3.1: library build and package candidate checks passed.
node --test packages/inkra/test/journey-map-*.test.mjs packages/inkra/test/tabs*.test.mjs packages/inkra/test/travel.test.mjs packages/inkra/test/package-boundaries.test.mjs: 60 passed, 0 failed, 0 skipped.Before upstream integration, focused Chromium checks passed for labels/gaps, moving custom content, selection isolation, responsive Tabs, keyboard and focus behavior. These are focused checks, not full browser or real Safari acceptance.
Node 22 / React 18 remains for CI validation.
Updated the export-inventory assertion for the new public default palette; the focused package-boundary tests now pass. The initial CI failure was confined to that outdated assertion.