I propose to create a new block for Thunkable X. it should work like the obfuscated text block from Thunkable classic, plus the text in the block will be empty if you share your project. This could help us to hide our API keys
Yes this is important. What I do is I break my API key down into four small chunks. I then add a unique character string to each of those four components.
When i call the API, I read the list, assemble the parts, and delete the keys in one function.
Not perfect… but it does not allow the key to be stored in a single place.
This does not work for components that dont allow you to set the key in the blocks.
Requests for new features (as well as bug reports) are best entered in out external GitHub issues list (here). From there you can check to see if a similar request has been made and create a new issue if necessary (via the green “New Issue” button).
Issue entered there have a much higher chance of being noticed and prioritized than requests made in this forum.