I’m trying to figure out whether a particular behavior in an API connector is feature or a bug.
Here’s the scenario: when you set an API call parameter as ‘public,’ making it visible in the console, and then dynamically define its content within the app, everything seems to work smoothly. Surprisingly, even if you later reset the parameter as ‘private’ (invisible in the console), Bubble still functions with the dynamically defined value.
I’m curious – is this by design, or could it be a bug?
By “public” you mean a parameters with private box unchecked?
If you mark it as private, Bubble will use API Connector value (and even with public, if not set to allow blank). If you have set a different value while it was in public and now set it to private, I agree with @tylerboodman.
@DjackLowCode I have been using your nodeflow plug in and have an issue with one singular thing. I cant change the font color in any of the nodes even though their is an option to right in the node settings. Would really apreciate if you could help me out on this . thank you.
@DjackLowCode Hey jack , it seems I have found a new bug with the nodes. You cannot connect them together even when the option “nodes connectable” is “yes”. I have tried it on several apps and it doesn’t allow you to connect. If we could get this fixed , that would be greatly appreciated.
