Hey @Rakitha -
This is a good discussion to be having right now, we are actively working through what versioning might look like for custom widgets (along with a few other asset types in Tulip). Our current thought is that going into a widget that is already being used in a published app would create a new version of that widget in the background so you don’t end up with pete_test_widget_v1, pete_test_widget_v2, pete_test_widget_v3…
The issue with this approach is it wouldn’t necessarily resolve your usecase where you want those changes to be automatically deployed to a published app. If we did enable this functionality, how should we handle:
- Cases where props were added or removed? What about events?
- What about cases where there are the same props and events, but maybe the events signify something different in v2, than they did in v1?
Pushing changes to components being used in apps really circumvents all that we look to achieve with app versions. When you publish an app, we never want anything in that version to change. Having said that, we will find a good solution that resolves your pain point.
Keep the great ideas coming-
Pete