Offer more Builders when wrapping widgets

I’d like for the “wrap widget” context menu to offer a greater selection of builders, e.g., AnimatedBuilder and LayoutBuilder.

When it comes to single-child widgets, and even multi-child widgets, it’s easy to select a similar widget and then rename it. For example, if I want a Stack, it’s not available in the context menu, but I can easily select Column and then rename it. However, Builders are not so easily substituted.

Builders have varying additional arguments, e.g., Stream, Listenable, etc. Moreover, the builder delegate signature varies between Builders.

Providing more Builders would be a much bigger time saver for me than having a long list of interchangeable widgets.

[matthew-carroll]

@pq I guess I missed some of the followup messages here a year ago.

Here are some examples of what I’d expect to see generated for a few different builders:

LayoutBuilder(
  builder: (context, constraints) {
    [CODE_NEEDED]
  },
)

AnimatedBuilder(
  animation: [CODE_NEEDED]
  builder: (context, value) {
    [CODE_NEEDED]
  },
)

And then perhaps support for a “generic builder”, which won’t completely satisfy any builder, but would be a nice headstart for custom builders:

MyBuilder(
  builder: (context) {
    [CODE_NEEDED]
  },
)

I do think this is worth some UX investigation. CC @InMatrix

[matthew-carroll]

For me, personally, the structure is all that matters. I haven’t found much value in filling in the name of a widget. Instead, the value is generating the child: line or the children:[] array, or in the case of the builders, the actual builder function.

Builders are the most problematic because most builder functions differ in signature, and on top of that, they all take different required parameters.

I’m not the sure the heuristic of “widgets…most common in user code” is necessarily a good one because the frequency of use doesn’t reflect the tediousness of adding the widget. If you again consider something like LayoutBuilder, I may only use that once in my app, but I’d be far more appreciative of not having to lookup that builder function signature online than I would to have quick access to a Center widget, which only saves me a couple seconds vs the generic “wrap with widget”

PS - I understand that the needs of beginner Flutter developers may be different here. I am transparently saying this as someone who knows most of the widgets that are available.