Adding commenting functionalities like regular programming languages have would be great. The ability to label certain triggers or widgets with notes you might have is great.
Also the ability to comment out certain parts of a trigger would be very helpful when debugging.
Another thing I think would be great is adding a spot somewhere in the tulip editor for common triggers and widgets that you made, just like subroutines. So instead of copying and pasting, you can just invoke the ones you need.
Thanks @btolawak - agreed that having more documentation would be valuable.
Have you heard of the Functions feature in pre-release now? It will provide a spot in the Tulip editor for shared logic. We’d love to get you early access to preview - just contact your Tulip representative for access.
We’d likely try to add more comments and documentation to the Functions editor as the biggest win for this kind of change. After taking a look at Functions, let me know if you still think inline block comments in Triggers are still also separately valuable.
For reused Widgets - this is also in early consideration and discovery. We’ve been referring to this as “Components” in vision and roadmap presentations. I’d love to hop on a quick call to find our more about how you’d use a feature like Components or a library of reusable widgets. Let me know if you’d like to schedule a quick :15-20 min chat to go through your ideas!
- Olga
Also, welcome to the Community! Great first time suggestion 