Functions Where Used

Product Suggestions
1

Hey team,

Functions is slowly becoming one of my favorite tools about Tulip. It opens pathways to enabling democratized development while keeping central control and enabling some required complexity in an admin managed place. When working with large instances, this is a huge win for scalability.

I know that the team is aware of this, but I wanted to specifically articulate what I think is the primary remaining gap holding me back from completely switching to Functions across the board: the lack of Where Used on a function makes it impossible to understand the potential implications of your changes.

I can live without versioning and a lot of other things, but I would highly recommend that this gap be prioritized so that large instances can comfortably start using functions at scale.

Happy Tulip-ing!

2

Hi @danielpomeranz and thank you for the great post.

Good news- Where Used is the next feature we’ve prioritized for Functions and our focus this quarter. Agreed with you this is the biggest opportunity for the Functions feature set today, and we’re actively working on closing it. It will take some time to close as for this feature to be performant, we have to do some backend schema refactoring, which we’re investing in now.

Appreciate the insightful input as always & keep them coming!

-Olga