fix: resolve travel anchor ID collision for repeat city pairs
Include segment index in travel anchor IDs ("travel:INDEX:from->to")
so Follow Team trips visiting the same city pair multiple times get
unique, independently addressable travel segments. Prevents override
dictionary collisions and incorrect validDayRange lookups.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -273,7 +273,7 @@ final class ItinerarySemanticTravelTests: XCTestCase {
|
||||
|
||||
let constraints = ItineraryConstraints(tripDayCount: 4, items: [gameItemA, gameItemB])
|
||||
|
||||
let travelValidRanges = ["travel:citya->cityb": 1...4]
|
||||
let travelValidRanges = ["travel:0:citya->cityb": 1...4]
|
||||
|
||||
let validRows = Logic.computeValidDestinationRowsProposed(
|
||||
flatItems: items,
|
||||
|
||||
Reference in New Issue
Block a user