Awesome @bradlymathews!
We are implementing a new product and yesterday we launched it for our first users. I'm in love with Retool and all the possibilities to build something amazing in a short time. However, yesterday we were heavily impacted by some of the latest bugs that have surfaced.
First, something that was working in the tests stopped working and we thought we had broken it, however it was an error in the platform itself (Row doesn't get selected when we click on the action buttons in a table row).
Then, during the onboarding of new users, we noticed the problem with setState. It took a few hours before we realized that we didn't actually change anything and that it was Retool itself that broke the functionality.
It's very cool to see that Retool team is working on improvements, but it's quite worrying to realize that errors come "out of nowhere", taking away our trust and of our customers in what we are building.
We developers know that bugs happen and sometimes we only notice it when we bring the code into production. However, the frequency that we encountered some impediments surprised us. We expect the quality requirements to increase to prevent something from breaking this way. In the meantime, we'll commit to being more present in the community to let you know what we find.