This meeting was between the State Changers as they attempted to troubleshoot issues related to sending an array into a channel using tools like Xano and WeWeb. The team encountered complications when manipulating arrays of objects, ultimately discovering that the database they were working was more complex than necessary. The main issue revolved around the intricate arrangement of objects within lists, and their association with 'mesh bank movements'.
The meeting produced two key insights: 1. Simplification at the database level can be tremendously beneficial. Having one level of complexity (either lists or objects but not both) can prevent problems from escalating as work continues in backend and frontend code. 2. Errors can arise when working with Xano. When encountering issues that are not solved by refreshing or minor tweaks, recreating the work often solves the issue, indicating that the problem is not due to the users but the tool itself. Keywords addressed includes "Xano", "WeWeb" and "State Change". The discussion did not touch on the following: "FlutterFlow", "Zapier", "Make", "Integromat", "Outseta", "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Javascript", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda", "serverless", "ScriptTag", "OpenAI", "AI21". During the meeting, a useful solution was discovered which simplified the input to the database, which was then successfully tested at the end of the session.
(Source: Office Hours 6/16 )
