22 March: Plugin and Compilator bug fixes

This week we released mostly critical errors repairs for the plugin.

Fixed 🔧

Issues with the user's access token in Figma during the onboarding process

Sometimes the onboarding process fails because it sends an error message regarding the user's token.

The issue primarily occurs when the user hasn't registered their Figma token on our platform, or their token has expired, or there is some issue with obtaining their token in Auth.

The solution to complete the onboarding was to remove the validation step for creating a project since this data is not a requirement for project creation.

Compilation issues with the positioning of an instance and problems compiling shadows

When an instance lacks autolayout, its positioning and that of its siblings were being compiled incorrectly. Additionally, the shadow of elements doesn't appear as expected on components with fill.

The positioning issue was that when an instance didn't have autolayout defined, it occupied all the space like a block. The problem with the shadows was that the configured fills were not being taken into account.

The solution for the positioning was to default instances to have the "inline-flex" property so that they have it and occupy the space in the DOM flow as configured by the user. The solution for the shadows was to check the fill of an element; if it doesn't have a fill, it will be compiled as a "filter-drop-shadow" property, and if it does have a fill, it will be compiled as a "box-shadow."

Problems with the user experience when configuring text data in the parameters in the plugin

The user had an incorrect experience when adding values to scalar parameters. The problem occurred

because there was a bug when checking the data type of the parameter. An upperCase was added to

the string to be checked to prevent it from failing.

Incorrect and unselected visualization of objects as values in the plugin

The user had an incorrect user experience as they were unable to select elements from a data source representing an object (list or object from a query). Additionally, the data of these elements was not displayed correctly, resulting in a broken user experience for selecting values from a data source.

A code refactoring was performed in the recursive method responsible for displaying the object's elements, enabling them to be selected as well.

Incorrect saving of nested property data in the plugin

A value representing attributes of nested objects within a user-selected query was not being saved, causing compilation errors.

A parameter was added to allow obtaining the exact path in the data tree of the query for the attribute being displayed.