Issue handling function passed as children in React components

Open
  • Is something wrong?
#333 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
react, typescript
Domain
developer-experience

Research direction

Start by tracing how Code Connect handles figma.children("*") and renders the example callback in its React support; the issue does not name relevant files or tests. Check how function-valued children are represented and whether slot attributes can be forwarded. Done means documenting or supporting a way to render the function child and pass its attributes to the rendered component; the issue has had no comment for 243 days.

Written by the indexing model from the issue text.

Description

API question

Please provide:

  • Code Connect CLI version: 1.3.6
  • Operating system: macOS Sequoia 15.0
  • Code Connect file, Figma design and/or relevant code snippet that could help us get more context:

I have a React component where I’m using an arrow function as children to pass click events and other attributes down to a slot node (in this case, a Button):

<DropdownMenu.Trigger>
    {(attributes) => <Button attributes={attributes}>Open</Button>}
</DropdownMenu.Trigger>

However, when I try to connect it using Code Connect, the API doesn’t seem to handle a function passed as children for DropdownMenu.Trigger.

Here’s my setup:

figma.connect(
	DropdownMenu.Trigger,
	"https://www.figma.com/design/...,
	{
		imports: ["import { DropdownMenu } from '@library'"],
		props: {
			children: figma.children("*"),
		},
		example: ({ children }) => <DropdownMenu.Trigger>{(attributes) => children}</DropdownMenu.Trigger>,
	}
);

Result:

Image

Additionally, how can we pass the attributes parameter down to whatever component is rendered inside the slot?

Thank you!

Dominant language
TypeScript
Stars
1.6k
Forks
126
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from figma/code-connect

All issues in figma/code-connect

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.