August 2023 Summaries

The Frigade Forms SDK has introduced support for asynchronous validation between steps or pages in a form through the validationHandler prop on the <FrigadeForm /> component, allowing developers to prevent users from proceeding to the next step until an asynchronous call, such as a database or API call, is successfully completed. This feature addresses developer feedback by enabling the blocking of user progression until these asynchronous processes finish, ensuring that necessary validations occur before continuing. The implementation is demonstrated in an onboarding flow example where the validationHandler is used to send data to a database and confirm the success of the call, indicated by a loading symbol in the button. To utilize this feature, developers need to update to version 1.35.29 of @frigade/react.

The Frigade Forms SDK has introduced support for asynchronous validation between steps or pages in a form by utilizing the validationHandler prop on the <FrigadeForm /> component, allowing developers to prevent users from proceeding to the next step until an asynchronous call, such as a database or API request, is successfully completed. This feature, showcased in the onboarding flow of Frigade's own application, ensures that users are prompted to wait for the validation process via a loading indicator, enhancing the reliability of form submission processes. Developers can implement this functionality in their codebase by updating to @frigade/react version 1.35.29 and using the validationHandler to manage async validations effectively.

Frigade's component library has been significantly updated, featuring redesigned components with updated layouts and flows, and enhanced interactivity within the Frigade dashboard and component detail pages. Users can now interact with and experience each component to understand their functionality and user experience prior to integrating them into their products. To access these updates, users need to ensure they have version 1.35.14 or higher of @frigade/react.

Frigade has released a significant update to its component library, featuring redesigned aesthetics, updated layouts and flows, and enhanced interactivity in both the dashboard component and component detail pages. This update allows users to view and interact with components to understand their functionality and user experience before integrating them into their products. To access these improvements, users need to be on version 1.35.14 or higher of the @frigade/react library.

Frigade has introduced the ability for all plans to access multiple environments, allowing users to maintain separate instances for development, staging, and production. This feature facilitates the development and iteration of Flows by enabling easy switching between environments. It also helps prevent ID collisions between development and production environments and ensures that Reporting and Analytics data remain clean and organized.

Frigade has introduced a feature that allows all plans to access multiple environments, enabling users to maintain separate instances for development, staging, and production. This enhancement facilitates the development and iteration of Flows by allowing easy switching between environments, which helps prevent ID collisions between development and production phases. It also ensures that Reporting and Analytics data remains clear and organized within Frigade.

Frigade has significantly upgraded its developer documentation to enhance onboarding and adoption, introducing features such as an AI Chatbot for interactive engagement, a reorganized structure for better usability, a components section with ready-to-use code snippets, and comprehensive setup guides for various features like forms and announcements. The team is committed to continuous improvement and values user feedback to further refine the documentation, emphasizing the importance of community contributions in this latest iteration.

Frigade has announced a significant upgrade to its developer documentation, aiming to enhance onboarding and adoption of its tools. The improvements include an AI Chatbot for interactive engagement, a reorganized and intuitive structure, a dedicated section for components with easily accessible code snippets, and clear setup guides for various features like forms and announcements. These changes follow months of incremental enhancements, and Frigade emphasizes its commitment to further refining the documentation based on user feedback, highlighting the importance of community contributions to this development.

Frigade has introduced a new Content Editor for its platform, designed to facilitate the editing of Flow content without the need to manage the underlying YAML structure. Users can seamlessly switch between YAML and Content editing, with changes reflected in both formats as they are made. Currently, the editor supports only first-level steps of a Flow, requiring deeper structures like Forms to be handled with YAML. A "Preview" button is also available, allowing users to see live updates of their Flows, and a fullscreen option provides additional space for editing larger components. The introduction aims to accommodate those who may not be as comfortable with markup languages, enhancing accessibility and usability for a broader range of users.

Frigade has introduced a new Content Editor designed to simplify content updates in Flows by allowing users to switch seamlessly between YAML and Content editing modes, with changes being synchronized in real-time. This feature currently supports editing the first-level steps of a Flow, requiring users to revert to YAML for more complex, nested structures. Additionally, a "Preview" button provides a live rendering of the Flow, aiding in accurate content verification, and a fullscreen option in the preview pane offers more space for larger components. This development caters to users who may find markup languages cumbersome, enhancing usability while retaining the robust capabilities of YAML.