I’ve used loops quite a bit, and have optimized some of them using connectors, but in general I’m forced to use a loop in one of the following scenarios, but usually multiple all at once:
- I need to create/reference an arbitrary number of records
- I need to pull data from multiple tables and use that to create a new record / string / etc.
- I need a nested if/then operation
The three loops I have in my app right now are a bit too complicated to quickly explain, but I can try and distill their essential elements next week. I would also be happy to walk the product team through what I’m doing for 30 minutes as well.
Just my two cents but I think if loops and nested if/then statements or triggers are implemented it would be nearly essential to have commenting abilities within Tulip. Both in the literal sense of making comments to explain what’s going on, but also “commenting out” lines of code. It’s pretty hard to keep track of everything right now when building up a loop.
One other note is that 2 out of my 3 loops I have to restrict the user input so I don’t hit the 100 trigger limit. In some cases the 100 trigger limit is useful because the computation time just gets too long, but in other cases its just an inconvenience.