Uncodie
Technical DocumentationNo CodeTutorialsChangelogDisccord
Changelog
Changelog
  • Uncodie Q4 2024
  • October 2024
    • 18 Oct 2024
    • 29 Oct 2024
  • September 2024
    • 5 Sep 2024
  • July 2024
    • 5 July: Improved compilation
  • May 2024
    • 24 May: Database Roles
    • 17 May: Improved Compilation Times
    • 3 May: DB User access for every project
  • May 2024
    • 24 May: Database Roles
    • 17 May: Improved Compilation Times
    • 3 May: DB User access for every project
  • April 2024
    • 12 April: Onboarding
    • 5 April: Fixed Amazon S3 buckets integration
  • March 2024
    • 27 March: Several plugin fixes
    • 22 March: Plugin and Compilator bug fixes
    • 15 March: Improved SVG support and bug fixes
    • 8 March: Loading Component and several bug fixes
    • 1 March: Chart component and sections compatibility
  • Februray 2024
    • 22 February: Several plugin fixes
    • 6 February: Plugin available in the Figma Store
Powered by GitBook
On this page
  • Fixed 🔧
  • Error assigning a component type button in the plugin
  • Actions couldn't be saved in the plugin
  • Issues when generating styles passed to an instance
  • Visual error while refreshing project data in the plugin
  • Issues generating visibility rules for responsiveness

Was this helpful?

  1. March 2024

27 March: Several plugin fixes

We detected critical errors in the plugin preventing users from saving actions and setting button components.

Fixed 🔧

Error assigning a component type button in the plugin

A failure when performing the verification of the saved values prevented them from being saved.

The solution was to correct a type that was found within the validation function.

Actions couldn't be saved in the plugin

When attempting to add an action from the plugin, it was not being saved due to a reference error to a function that was recently added within the properties of the object being saved in the node.

The solution was to add a function before saving in the node that attempts to create a new object from its value and then send it for saving. If it cannot perform this action, it is sent as it was sent before.

Additionally, the origin that only affects the actions was removed because it is no longer required, but the previous function is still retained to prevent repetition.

Issues when generating styles passed to an instance

The user, when configuring inline styles from Uncodie to an instance, was not compiling the configuration set by themselves.

The problem was that the value passed to the component was incorrect.

The solution lay in implementing correct logic so that the styles could be generated correctly.

Visual error while refreshing project data in the plugin

Clicking on the Refresh action did not provide any visual signal that the process was ongoing, causing the user to associate it with the button not working.

The solution was to display a loading indicator when the action is executed and hide it when the updated data is obtained.

Issues generating visibility rules for responsiveness

When configuring responsiveness visibility rules for elements, they were not compiling correctly.

The problem existed because the correct operators were not updated in the compiler, and it was not taking into account that the data isShow could be undefined.

The solution was to update the operators for both single and multiple rules and assign a default value to the isShow variable when it is undefined.

Previous5 April: Fixed Amazon S3 buckets integrationNext22 March: Plugin and Compilator bug fixes

Last updated 1 year ago

Was this helpful?