The idea is:
There are a lot of node updates on a constant base. But sometimes (and from my experience, is happening quite a lot), the newer version does not suit us any longer, because many assumptions were made and some function had to be removed for some reason.
My use case:
I have a form trigger, that responded with a webhook. After updating it, the flow simply stopped working because the option to respond to webhook was removed. So, I needed to go back to the previous working version for my flow. Hence, I had to copy the node to a notepad, change the version, and copy back. So, on the settings, the version should be a simple dropdown where you can change the version to whichever you like.
I think it would be beneficial to add this because:
Newer versions of the node, can sometimes break our flows. Hence, it would be useful to be able to change it back. And adding a dropdown menu already filtering with all available version, rather than trying to find or guess which versions are available, would be very helpful and save tons of time.
Going a bit further, when adding a new node, the version should be visible there also.
Any resources to support this?
Node version that was was 2.0 and the updated 2.2 does not have the webhook any longer. As a rule of thumb, my guess is that you should never remove features UNLESS you have to.
Are you willing to work on this?
Don’t have the programming skills for it.