Deleting an input widget deletes the associated data lake variable

[ES-Alexander]

Bug description

Input Widgets allow manually setting Data Lake variable values, but are not the only way to do so. As part of the widget deletion mechanism they seem to delete the linked variable, which then breaks anything else that was trying to use that variable.

Steps to reproduce

1. Create two input widgets, and link them to the same data lake variable
2. Delete one of them
3. The variable is now gone, and the other widget no longer works

Primary pain point(s)

Actions and other Widgets that were using that variable get broken, with no obvious reason or warnings.

Additional context

#1688 introduced the option for multiple Input Widgets to share a variable (e.g. across Views, or just as different interfaces to the same value), so it seems extra likely people will run into this now (e.g. if changing a View to no longer include a control for a variable, that variable will then inadvertently be removed from other Views as well).

Prerequisites

• I have checked to make sure that a similar request has not already been filed or fixed.

[ArturoManzoli]

Well observed. This was intentional in the original design of the input widgets and should indeed have changed when the data-lake variable sharing update was implemented.