Utilizing the "Xano" API, one of the State Changers talked through his thought process and methodology for constructing a slider with the data received from this API. Having run into issues initially, the team member explained his streamlined approach as he attempted to resolve the problem, which involved generating a specific number of slides based on the information received from the API payload, and populating these slides on the client-side machine. Complications arose when dealing with data attributes and its translation into his HTML construction.
The discussion progressed into examining the code and iteratively debugging, questioning, and solving technical issues. One of the staff's observations was that the code was trying to append the slider construct before the data from the Xano API has populated it, potentially causing conflicts.
The solution proposed was adjusting the timing whereby after the data from the Xano API is fetched and populated onto the page, only then is the slider [Splide] mounted. This new approach was in response to a recognized timing issue. The State Changer confirmed having encountered this issue previously during the implementation of static demos on Webflow.
The meeting ended with an admonition for the team member to fine-tune his HTML generation and corresponding CSS to support the functionality of the carousel slider. The overall goal is ensuring the slider is fully operational, with data dynamically fetched and loaded from the Xano API.
(Source: Office Hours 12/19 )