I understand that new versions comes with new features. But breaking the userspace and old workflows is simply not good. And this is what happened to all my workflows now with version 0.3.30
I have now to test and recreate all my old workflows since the new version broke quite a few things. They now simply crashes at the mtb node. And this will produce quite a few unhappy bunnies in my user base. They don’t know how to fix it. They download the workflows from my page and expect it to work.
MTB string replace node has become dysfunctional. KJNode needs to be recreated since it shows a big gap. And that was just the two most obvious broken nodes. I wonder how much more is now not longer functional or shows some odd behaviour.
Of course, it’s the job of the node developers to fix their broken nodes. But it is you who broke it by changing the API. Before the current version v0.3.30 these nodes worked just fine.
As a side note, the new features to remove the convert input to text and vice versa is imho a bad change. It is not longer easy to discover by the user. You now need somebody to tell you. Or you stumble across it by coincidence. And that’s against one of the simplest UI UX design rules. The UI must be target leading and self explaining.
So please, be a bit more careful with future changes. Thank you.
Arunderan
