Version 4.5.5

What's Changed

• Added second and millisecond units to duration token by @mitchdotdeveloper in #173
• feat(): add contributors; bump dependencies

Full Changelog: v4.5.4...v4.5.5

Summary of changes

Adds a new durationUnit value (s or ms). Also bump dependencies and adds full contributors lists to README.md and package.json.

New Contributors

• @mitchdotdeveloper made their first contribution in #173

Version 4.5.4

What's Changed

• Addresses #170 — https://github.com/mikaelvesavuori/figmagic/issues/170
• fix(): add missing return to getEnvUrl() in configuration setup

Full Changelog: v4.5.3...v4.5.4

Summary of changes

Minor fix for a miss that probably came in the recent refactoring work.

Version 4.5.3

What's Changed

• Partly addresses #167 — https://github.com/mikaelvesavuori/figmagic/issues/167
• refactor(): improve support for non-standard layer compositions such as only text-only groups when generating Elements
• refactor(): remove useless try/catch blocks; config(): remove 'lib', importHelpers, and sourceMap from tsconfig; refactor(): minor fixes for return types and JSDoc comments
• chore(): set types on 'any' use-cases; chore(): remove 'wait' call
• chore(): set types on 'any' use-cases
• refactor(): continued work on using basic types instead of 'any' and minor work on reformatting to camelCase on vars
• refactor(): continue removing 'any' and setting better types
• refactor(): yet more work on adding proper types and minor code/docs refactors
• refactor(): continue setting types, should now be very few 'any' usecases
• refactor(): move from uppercase consts to lowercase in all files in 'frameworks' folder
• refactor(): move from uppercase consts to lowercase in all files in 'usecases' folder
• refactor(): move from uppercase consts to lowercase in all files in 'entities' folder
• docs(): add product vision document
• refactor(): take care of minor SonarCloud code complaints
• ci(): fix npm commands for docs generation
• fix(): update typedoc output folder and remove generated docs
• docs(): add version 4.5.0 announcement bit in README
• refactor(): fix code smells
• fix(): ensure there are clear error messages from the API call if an error occurs; remove unnecessary 'else'
• release(): bump version and update dependencies

Full Changelog: v4.5.2...v4.5.3

Summary of changes

This release contains mainly under-the-hood improvements, such as refactoring.

A user-facing improvement, however, is that API errors will now be correctly output rather than be masked in a catch-all message that may have (in certain cases) been misleading of the actual error.

Version 4.5.2

What's Changed

• #165 — Variants only working correctly with duplicate layers
• fix(): add check to removes empty subclasses for generated elements
• fix(): use randomUUID() instead of Math.random() to calc temp IDs
• feat(): accept INSTANCE as input for generating elements
• fix(): change ID type to string; fix(): add extra check for leading underscore for child elements
• docs(): update elements documentation
• refactor(): break up FigmagicElements nested CSS logic into separate functions
• fix(): update getUniqueValues to only use first occurrence of a property (previously it matched the full line: key + value)
• tests(): update "wrong" test to work with unique CSS properties

Full Changelog: v4.5.1...v4.5.2

Summary of changes

This release adds a number of smaller fixes that are mostly "under the hood". Most interestingly you are now able to use component instances as "input" when generating Elements, which could cut down on your redundancy and boilerplate when making variations (like buttons). This is still early days, so your mileage may vary on this feature.

What's become apparent during work on #165 is that the flat and nested elements code bases are pretty dissimilar and I'm reminded of how they really should be synced. The deduplication done for nested elements is not strictly 1:1 with how it works for "flat" elements meaning you may end up with duplicate properties. This is now addressed. Note that this change may impact your currently generated elements.

Version 4.5.1

What's Changed

• Fix: Ensure that a prefixed underscore character allows ignoring Figmagic Elements that reside in the "root" of the Elements page. This need is implied in #164 and partly addresses that issue.
• Docs: Update terminology to substitute "variant" with "style".

Full Changelog: v4.5.0...v4.5.1

Version 4.5.0

What's Changed

• Allow use of frames when making elements; closes #162
• Update docs to reflect change
• Better formatting (shorter lines) of JSDoc annotation for FigmagicElement
• Cleanup test files and update test payload with updated template contents

Meanwhile, the Figmagic Design System template at Figma is updated for the first time in a while. It now contains a example (among other changes) of using frames instead of groups in nested Elements.

Full Changelog: v4.4.6...v4.5.0

Version 4.4.6

What's Changed

• Adds support for frame-nested graphics; Graphics frames by @smmccabe in #156

New Contributors

• @smmccabe made their first contribution in #156

Full Changelog: v4.4.5...v4.4.6

Version 4.4.5

What's Changed

• #154 — Fix for shadows missing correct value (Y), previous fix was only partial.

Full Changelog: v4.4.4...v4.4.5

Version 4.4.4

What's Changed

• #155 — Zscaler Blocking Access to Figma API, Getting "Error: Missing one or more of required arguments: "figmaToken", "figmaUrl""

Full Changelog: v4.4.3...v4.4.4

Summary of changes

This version adds basic support for using a custom key and certificate when making API calls. See Node.js documentation on https.

To use this feature, Figmagic will look for key.pem and cert.pem in your current working directory. This is currently not customizable.

Version 4.4.3

What's Changed

• #152 — Elements are imported twice, in two different places

Full Changelog: v4.4.2...v4.4.3

Summary of changes

The previous implementation(s) around setting correct paths for generated files was messy and lead to a bug where files, in certain cases, would be generated in the intended folder and in a lower directory.

It's now cleaner and easier to understand the implementation(s), and the changes seem to correctly address non-trivial use-cases where nested paths are used.