Closed
Description
Observed behavior (please include a screenshot if possible)
When adding stops to certain patterns in the Editor, at times an uncaught error will be thrown causing the application to freeze up. It appears to happen for stops that have control points that are out of order (e.g., the control point for stop 1 has a greater shapeDistTraveled value than stop 2) or that are not located near to the stops themselves.
Expected behavior
After some investigation, it appears that this error is recoverable, so the application should certainly not throw an uncaught error. In general, we should avoid this because it causes a confusing experience for users. There are probably some enhancements we can make to help users resolve any control point issues more easily.
Steps to reproduce the problem
Steps shared in company chat.
Any special notes on configuration used
N/A
Version of datatools-ui and datatools-server if applicable (exact commit hash or branch name)
latest dev