I think there is something off about how rotation and radius are computed based on the transform. I've created a test file with two equivalent radial gradients. The results look like this (numbers rounded for clarity):

// both have size 300x600

// A
transform = [[ 0, -0.5, 1], [ 0.5, 0, 0.5]]
radius = [300, 600]
rotation = 90

// B
transform = [[0.5, 0, 0.5], [0, -0.5, 1]]
radius = [300, 600]
rotation = 0

Notice that A has a rotation of 90, whereas B as a rotation of 0. Since all other params are the same and they render the same, if I were to convert the radius and rotation to SVG params then A would render incorrectly.

It also may be the case that radius and rotation cannot be used in conjunction, then I will need a different solution, perhaps using the matrix directly in an SVG.

1. Figma color <–> RGBA.
2. Figma color <–> HEX.

Given a hex color #010b1d I convert it to "Figma RBG" by using hexToFigmaRGB("#010b1d") then apply the color to a node in Figma. The end color applied to the node is #000A22 which is very similar but not exactly the same. I assume is due to the Math Figma does to convert from "Figma RGB" to "Web RGB".

Is there any way I can ensure the color applied in Figma is my source value?

Thanks.
Regards

The api gives us access to the absolute bounds of a node however when shadows, strokes and blurs are added to the node this isn't taken into account.

My request is to provide a function which computes this offset/bounding box.

When importing functions that use lodash, the bundle size increases because it's importing every lodash function.

Changing the import syntax like so should fix these instances:
from: import { foo } from 'lodash'
to: import foo from 'lodash/foo'.

What is the best...lightweight way to document what each plugin function does?

We could definitely add to the readme, but I was thinking as a starting point if everyone can make sure there is a comment line or two in each function that explains what they do so its more obvious to users.

Thoughts?

Hey,
I seem to get an error every time I try to use an helper function (specifically loadUniqueFonts or getBoundingRect, didn't try others) and then run the plugin locally on Figma for Windows 10. When I remove all of the usages my plugin runs, adding a call to an helper function prevents the plugin from opening and yields this error on Figma console:

TypeError: Cannot read property 'Symbol' of undefined
    at Object../node_modules/lodash/_Symbol.js (VM1261 PLUGIN_9_SOURCE:18085)
    at __webpack_require__ (VM1261 PLUGIN_9_SOURCE:20)
    at Object../node_modules/lodash/_baseGetTag.js (VM1261 PLUGIN_9_SOURCE:18902)
    at __webpack_require__ (VM1261 PLUGIN_9_SOURCE:20)
    at Object../node_modules/lodash/isSymbol.js (VM1261 PLUGIN_9_SOURCE:23264)
    at __webpack_require__ (VM1261 PLUGIN_9_SOURCE:20)
    at Object../node_modules/lodash/_isKey.js (VM1261 PLUGIN_9_SOURCE:21458)
    at __webpack_require__ (VM1261 PLUGIN_9_SOURCE:20)
    at Object../node_modules/lodash/_castPath.js (VM1261 PLUGIN_9_SOURCE:19909)
    at __webpack_require__ (VM1261 PLUGIN_9_SOURCE:20)

I understand it may seem like a lodash error, but as I mentioned when I remove all of @figma-plugin/helpers usages, there's no error. BTW, running the same code with all the usages on Mac seems to work without having this error.

Worth adding, on version 0.14.3 the same behavior happens, with a different error that is more indicative towards the helpers package. I updated to the latest version before opening the issue to check if it was already fixed.

Let me know if I can provide more details about it. Thanks!

Idea to add helper that will handle all stuff to set characters to TextNode:

1. load font (load and set fallback if fails)
2. set characters

Think about ways how to keep multifont styling

isTypeNode.d.ts

test file: https://www.figma.com/file/sidppHshZlzQ9UM1TAfgcC/findAll-test?node-id=0%3A1

findAll(figma.currentPage.children, node => true)
returns 2 nodes

figma.currentPage.findAll(node => true)
returns 7 elements (the number of nodes in the file)

This method fails for nested instance nodes which have rotated children. It is not possible to add the group to the instance.

in group: group() failed: Cannot move node. New parent is an instance or is inside of an instance

Related conversation:
https://figmaplugins.slack.com/archives/CHPTY6TFD/p1592231931354600

Proposed solution by @steffanwilliams:
https://gist.github.com/steffanwilliams/4d4be23780eb10dcd238200cf297b1b5

Need to complete project configuration by adding autoprettifying on git hook with husky and lint-staged.

Hi! I was reading the docs and saw that the findAll method is a "Custom implementation of the figma.findAll method, which runs x1000 times faster". I looked at the code but couldn't understand why. Do you mind explaining?

I'm getting an error when using the clone() helper. I believe it's because of a circular dependency problem, but that's just a hunch.

When I run clone(figma.createFrame()) I now get the following error:

RangeError: Maximum call stack size exceeded
<ref *1> LayoutMixinStub {
      type: 'FRAME',
      children: [],
      parent: ChildrenMixinStub {
        type: 'PAGE',
        children: [ [Circular *1] ],
        parent: ChildrenMixinStub { type: 'DOCUMENT', children: [Array] }
      }
    } []

Could it by trying to loop through the parent, which then loops through the children and then through the parent again?

The containing FrameNode is at [0,0]
The TextNode is reversed and getBoundingRect incorrectly reports y = 42

How about to make these helpers as npm-package?

Am i allowed to copy the code and use it for commercial usage? Or should i only use it by the package itself?

https://github.com/figma-plugin-helper-functions/figma-plugin-helpers/runs/2319016555