8 March: Loading Component and several bug fixes

Now you can use the Loading component in Uncodie projects as a placeholder for your elements as they wait for data.

✨New

Loading Component

We added the loading component to facilitate the usage of loading placeholders, the lading component is 100% compatible with Uncodie Figma to Code animations and transitions, so you can create a general loading UI for your app or select individual loading placeholders for each query and screen in your app.

Changelog

We are now registering every fix, update, and new feature released on the week in a dedicated public channel to help users keep track of Uncodie's evolution and status.

Improved 💪🏼

Added Chart types on the chart component

Now you can select the type of chart you want to render while using the chart component changing the type parameter to the desired chart style.

Components Documentation

Added a complete list of the current Uncodie out-of-the-box components in the plugin, and updated component names and parameters for a better user experience.

Fixed 🔧

Backoffice

Problem updating scripts in a project in the backoffice, preventing the new version of a script from being added to the project in the Plugin.

The plugin progress bar shows an error every time you publish a project

The plugin showed an error message on every publishing process due to a compiler warning causing the process to file in the API even when the deployment continued successfully.

Problems in option selectors

Selectors can display complex data structures for the actions and with dynamic values. The plugin now uses a selector where the data displayed in the selector option differs from the value stored in the system.

Problems in the Data section

We fixed an issue making the plugin crash while handling collection queries. The analysis of the property OrderBy caused the plugin to crash because of an undefined property in the queries.

Problems in UI freezing while selecting a new node in the Figma file

Solved a problem presented when the new node didn't have any parameters for the plugin section to show, the plugin showed the last selected node instead of showing the section empty causing confusion and entry errors.

CSS changes not being saved

Problem with the CSS editor that prevented the current changes in code been saved. The timer in the update function was too slow and the changes were lost if they were written too fast by the user in the plugin.

Scripts not being added to a file while compiling

External scripts are now correctly being added to a project. The problem originated due to a refactor in the script's data structure on the Figma file local storage. The deprecated structure is now handled in the CLI to support legacy projects.

Responsive design errors while using Figma sections

Apps were rendered with errors in the layout handling due to a misinterpretation of sections as a frame without layouts.