This is a little difficult to test, but it fixes the same issue that was present on the plan creation form where the inputted name was being reset if any of the plans were updated. This was due to a reactive statement that was resetting the field because it took the plans list as a dependency. This was only rarely observable during the e2e tests as they run multiple tests at the same time that affects the plans.
This also probably actually maybe fixes all the flaky tests?
This is a little difficult to test, but it fixes the same issue that was present on the plan creation form where the inputted name was being reset if any of the plans were updated. This was due to a reactive statement that was resetting the field because it took the plans list as a dependency. This was only rarely observable during the e2e tests as they run multiple tests at the same time that affects the plans.
This also probably actually maybe fixes all the flaky tests?