What does an API change touch?
A developer wants to change how vehicles are assigned. We check which backend calls a view makes and what the change affects, down to the calling components.
Transcript
A developer wants to change how vehicles are assigned, but first wants to know what it affects. We ask as a developer: which backend calls does the container order details view make? Acting as an agent, the chat goes through the map's 264 files, and the answer comes together in a few seconds.
Five endpoints: querying vehicles and containers, then assigning the container, the vehicle and the emptying location. We follow up: if I change this, what does it affect in turn? The answer is again based on the map, and now it looks from the other direction: three other components, on two screens.
And a trap: the order list also calls vehicle removal, with the same parameter. The same is there with a few clicks. We close the chat and open the module's interfaces.
In the list we find the vehicle assignment endpoint, and at the bottom of its page are the four calling components, each with the place of the call. Before anyone touches it, we already know what has to be retested.
