IssueTracker

Interesting idea - I've shared your request with the team.

Hey, thanks for considering this.

Of course, the idea could be applied to other places of the API as well, basically to all setter functions without
return value.

map.set_center(latLng).set_zoom(zoom);
marker.set_icon(foo).set_cursor(bar);
etc.

I discovered today that you have loaded a "fix" in production without telling anyone !

This fix is not acceptable because :
1. Even though there are no errors now, the modified DirectionsResult object is stripped of the other alternate routes once the line has been dragged.  Thus making it difficult to keep track of user choices.
2. Dragging will at times produce a straight "ghost" line on another area of the itinerary.
3. The dragging process does not respect the majority of the originally chosen itinerary, it will try to reproduce the first original proposition.

Feel free to come back to me in the case that you would like me to validate/test a solution BEFORE loading into production.

A fix has not been deployed yet. What is the regression in behavior you are seeing? Could you explain what you think we "fixed"?

1. Before my previous comments, the array of itinerary routes did not change.  If there were 3 alternative routes, then the array of 3 was still there after dragging.  This is no longer the case - only the selected route remains.

2. * New * bug - the ghost line mentioned above.

3. * New * bug - case 3 above.

All of this is new behaviour which can be seen in the test case I loaded for you before in comment #2, therefore leading me to the conclusion that a modification had been loaded into prod.