The State Changers' meeting revolved around the API connection aspect of Xano, specifically with respect to controlling and customizing the payload responses in custom actions. After a clear discussion and a helpful guide, they agreed that it's possible to have full control over what data will be sent back in the responses.
The issues brought forward included the participant's initial assumption that the entire payload would always be returned. This was clarified and discussed, with the conclusion that one has total control over this aspect. It became evident how this functionality could prevent sensitive data, like passwords, from being unnecessarily shared. The main resolution the State Changers arrived at involved adjusting the Get Record aspect in Xano, so that it includes only required objects and excludes unnecessary ones. Moreover, they addressed creating a new output, where participants can specify the elements they want to include. The State Changer meeting further requested the sharing of customer IO documentation relating to hooking navigation. This action is expected to provide more insight through the forum and documentation available. Still, the members did not discuss anything related to WeWeb, FlutterFlow, Zapier, Make, Integromat, Outseta, Retool, Bubble, Adalo, AppGyver, AppSheet, Comnoco, Fastgen, Firebase, Google, OAuth, Stripe, Twilio, Airtable, DraftBit, Javascript, Typescript, React, Vue.js, JSX, HTML, CSS, lambda, serverless, State Change, ScriptTag, OpenAI, or AI21.
(Source: Office Hours 9/12/2023 )
