During the meeting, the State Changers centered their discussions on troubleshooting issues with a page that searches nonprofits. They found an issue with the search query not loading initially and also identified that the form was refreshing in a way that was not intended. The discussion then focused on preventing the default action of the form to stop it from refreshing.
Further in the discussion, the State Changers discovered some errors in the code that prevented the search function from working properly. The form was not making the correct requests due to a low code issue. The group also dealt with a problem where received items were not defined. To handle this, changes were made in the code's structure, particularly lines of code were updated on lines 217 and 221 for synchronicity. Towards the end of the meeting, the group spotted a potential issue with the population process, realizing that the template may be deleted at the end. They considered using a hide function as a solution to this problem. The session ended with the group planning to continue work on these issues. During the meeting, they referred to a range of code-based elements and softwares such as JavaScript, Prevent Default, Propagation, Console Log, ScriptTag, Enter Button and others. However, the meeting did not include any discussions about 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, OpenAI, or AI21.
(Source: Office Hours 4/10 )
