In this meeting, the State Changers focused on troubleshooting and debug an issue with a date picker tool. The error message "uncaught reference error picker is not defined," suggested that the variable picker wasn't defined in the YouTube code sample being used.
The discussion started analyzing variables in script tags, in particular the picker variable. The State Changers believed that the picker might have been defined in the linked JS files within the script, but after further debate, it was suggested that maybe the picker wasn't being properly used within the code.
To solve this problem, a deep dive into the API documentation for Pick a Day took place, highlighting the importance of understanding the underlying APIs for the tutorials that are used. The group noted that most tutorials, especially those created by dev rel individuals, often focus on a simple, basic usage while skipping over the complexities and different use cases for that API. The problem was eventually identified as an issue with the picker object not being referenced correctly, and subsequent adjustments fixed the error.
A broader discussion was also prompted about the balance between leveraging no-code tools for basic things vs. developing more advanced coding skills to handle more complex, unique cases in your projects. The idea was to use no-code tools to tackle most use cases, but for the more unique situations and complex functionalities, actual coding can provide a more tailored solution.
Throughout the meeting, the script tag tool and picker were the main focus, but the broader conversation about learning and development within coding, the use of tools like Webflow and navigating through APIs to solve unique challenges also happened. The importance of research techniques and knowing when and where to narrow down your search was discussed, especially when dealing with errors and tricky code writing.
(Source: Office Hours 5/29 )