Cannot use Component parameters to Slot Child parameter in custom widget

[price-ibirama]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

I am implementing the new Slot Child feature in a custom component. Previously, there were parameters of the Widget Builder type to define “slots” that would be filled by other components (composition pattern). However, for the Widget Builder type, when passing it as a parameter outside the widget tree, it suggests a list of components in the FlutterFlow variable menu, but with the new Slot Child type, this doesn’t happen, suggesting only normal data types. I needed it to allow the same as Widget Builder so that the component with Slot Child could be used both in the widget tree and in custom widget actions (which open the FlutterFlow variable menu for passing slot parameters).

Expected Behavior

When defining Slot Child type parameters, when using the component in actions outside the widget tree, the variable menu should suggest components as a parameter.

Steps to Reproduce

1. Create a custom widget
2. Create a parameter of type Slot Child
3. Use the created widget in the EmptyStateWidget for lists (when using generate dynamic children) or in actions like BottomSheet::open, CustomDialog::show...
   You will see that it is not possible to provide the parameters because the variable menu does not suggest the correct types (components).

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT8sl8n17ZNPxeFY+Kryb8JVtDwWH0g8UI0vjsN+WQggIZD2PbAte877dhFpZ+mga1NEDWH8/TsJw/TKhuztBPo7NQiCc5xk1Lp1Qx7gYF2mVramCsyRdnZ8RNNMfWqn1sCRmhB4Ku5wd2wt32Wlf9itXjLtNKWzOGwFPvqlA97Pnmy5LB3zJSAz4wwXRHaZTI5ODEz25eKMrop5yfj/0w==

Visual documentation

Environment

- FlutterFlow version: 6.6.55+
- Platform: Windows Desktop
- Browser name and version:
- Operating system and version affected: Windows 11

Additional Information

No response

[Juansarmi]

Hello!
I’m sorry you’re experiencing this issue. I understand that for your use case, it would be more appropriate to use a Widget Builder parameter instead of a Child Widget, so you can use it without any limitations.

That said, I’ll go ahead and report this to our engineering team so it can be investigated further, and I’ll keep you updated as soon as I have any news.

Best regards.