In this meeting, the State Changers discussed various coding issues primarily related to JavaScript and FlutterFlow, with api chaining and implementing preconditions being the focal points. They tackled loading dynamics in an API, weighing the necessity of making the loading dynamic and how to curb possible errors during the loading process. The discussion touched on the usage of Visual Studio Code as an efficient tool for the task.
A considerable part of the meeting was spent on digging deeper into JavaScript, analyzing code, understanding response status codes and using them for error handling. A key takeaway was that a status of 200 to 299 suggests a successful request, while anything 300 and above indicates an error, which should ideally direct the user to a different page. Further, preventive coding measures, like adding the return statement after changing the href to avoid any additional code execution, were also discussed. The meeting wrapped up with the question of migrating these actions to FlutterFlow, where the limitations of embeds were considered. The participants indicated the possibility of creating a mini-website to facilitate the process on FlutterFlow in the future.
(Source: Office Hours 2/24 )
