Add the ability to see what endpoints are in use, and where they are used, from the API Connector

[anthony.schanen]

Hey bubblers,

I have been tasked with updating an older Bubble app that has had many iterations. Some bubblers before me (including myself) don’t clean up after themselves when working on an application. That means test data, API calls, endpoints etc. can get left behind after a project is complete.

Coming back to the project later, bubbles API connector is now filled with a huge amount of API calls, and I have no way to tell what is in use and what is not without forcing errors by making the calls fail (so the data looks wrong and generates an issue)

Lots of IDE’s (if you’re from a software background) will show you dependencies on classes, variables etc. As bubble is posing itself as a no-code IDE for web apps, I feel like this would be immensely helpful in both debugging and refactoring. As Bubble apps get older (into the 10 year mark) the need for this functionality is going to become rather large.

Let me know what you guys think!

[doug.burden]

I love this idea. Just somewhere on the bottom right they could display the ‘page’ name and the name of the action.

And maybe you could click on it and it take you to the page and the action.

[w.fly]

I use these two items in the “App Search Tool” – Not super elegant, but maybe it’ll help you in the interim to find where you are using the API as an Action (Screenshot #1) and using the API as Data (Screenshot #2)

Screenshot #1

Screenshot #2

[anthony.schanen]

This does help reduce some of the hunt and peck approach. Thanks for this!