Comparing version 4.3.1 to 4.3.2
{ | ||
"name": "figmagic", | ||
"version": "4.3.1", | ||
"version": "4.3.2", | ||
"description": "Figmagic is the missing piece between DevOps and design: Generate design tokens, export graphics, and extract design token-driven React components from your Figma documents.", | ||
@@ -5,0 +5,0 @@ "homepage": "https://www.figmagic.com", |
@@ -22,5 +22,5 @@ ![Figmagic cover art](images/cover.png) | ||
**The default uses a local soft delete by moving folders into `./figmagic-trash` – that's why you might be surprised by seeing it added.** | ||
Any deleted files are now permanently destroyed by the Node native `fs` module. | ||
Read more under the [`refreshType`](#refresh-type) listing. | ||
**Versions `4.3.0` and `4.3.1` used a flaky dual-mode, configurable pattern where you could use either a "hard" or "soft" delete mode (soft deletes meaning placing files in a local trash folder). _This is NOT supported and intended from `4.3.2` and forward as that was too buggy._** | ||
@@ -147,6 +147,2 @@ --- | ||
#### Overwritten files are moved to trash | ||
When running `figmagic`, files will be moved with the Node module [trash](https://github.com/sindresorhus/trash) (multi-platform) into your OS's trash can. Thus, you can recover anything _unintentionally_ overwritten. | ||
#### Folders | ||
@@ -553,15 +549,2 @@ | ||
#### Refresh type | ||
`figmagic [--refreshType | -rf] ['soft' | 'hard']` | ||
**Default**: `soft`. | ||
This defines how overwritten files will be "refreshed" when starting Figmagic operations. | ||
- In `soft` mode, the previous folder is renamed and placed in a Figmagic-created trash folder (`./figmagic-trash/`) with an added [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) timestamp (i.e. `2021-09-05`) and hour-minute-second indicator. | ||
- In `hard` mode, Node's `fs` module is used to erase the folder with no way of retrieving the old folder. | ||
--- | ||
#### Set REM size | ||
@@ -568,0 +551,0 @@ |
Sorry, the diff of this file is too big to display
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
157731
884