In this meeting, the State Changers primarily discussed debugging JavaScript. The primary issue highlighted was an error involving a variable that comes from a get request or user input. The variable was throwing an error when an attempt was made, to check the length of that string. The advised solution involved utilising console.log to analyze and understand what the string is perceived as before line 159. In addition, it was suggested the error might be due to the variable also being undefined, and that changing the code from checking for stricter equality to less strict could capture other possible problematic scenarios. Future plans include looking into a non-triggering Java click event. Tools involved were strictly JavaScript-based, so no mention of any other tech tools or languages like "Xano", "WeWeb", "FlutterFlow", "Zapier", "Make", "Integromat", "Outseta", "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda", "serverless", "State Change", "ScriptTag", "OpenAI", or "AI21".
(Source: Office Hours 2/16 )
