15 March: Improved SVG support and bug fixes

Now you can use SVGs both in web apps and animations with better precition, we have improved the docs on Uncodie for all components.

Improved 💪🏼

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 🔧

Errors in the Plugin and Compiler after deleting nodes in your project.

The plugin had different errors while deleting nodes, that affected the compiler, you can now reset a node setup without problems, the plugin used to store the last state of the node setup causing errors in the general usage of the plugin and compiler.

Instance properties are not being reflected

Properties were failing to display the correct or dynamic value once rendered in the app, changing the text, colors, or CSS props on instances of different components.

The cause of the problem was the generation of components as elements that had a configured mutation. This incorrect behavior generated an extra component layer that did not manage the properties.

The solution was to add a condition that only queries can be considered as components, not mutations. Additionally, the priority of texts was changed, where data binder configurations have higher priority than texts configured by props.

The scripts in the onRender event were not being executed

When configuring a script within an onRender event for a component, the expected script was not being executed as intended. The issue arose because, with the new plugin, the data was being saved in a different variable, resulting in incorrect data retrieval. A logic was added to retrieve the data from the old variable to ensure that the previous configurations continue to function, in case there is no data in the new variable.

Problems with the parameters of the data section

The parameters of the data section had lost the ability to obtain dynamic data and from a script. This affects the user as many of these parameters' data may come from another context or from a script configured by the user.

There were two fundamental problems in the implementation: scripts were not being resolved, and parameter management was not considering data coming from a context or a script.

Logic was added to correctly process the scripts, and parameter management with dynamic data was implemented.

Compiling SVG strokes issues.

When designing vectors and compiling them, they generated thicker edges than expected by the user.

This was because there was no correct logic to apply CSS styles to the vectors.

To resolve this issue, the fillGeometry and strokeGeometry properties are evaluated to compile the strokes as fill, thus the compiled vectors from Uncodie appear correctly.