Skip to content

Conversation

@Hixie
Copy link
Contributor

@Hixie Hixie commented Jun 22, 2017

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The previous paragraph refers to "widgets" as children, maybe say children here as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good call

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

builder => [itemBuilder] (because just "builder" unifies with ListView.builder)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed both to The 'itemBuilder' (with backticks) since it's not actually something hyperlinkable.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

using an item builder that returns a previously constructed widget. If the list view's children are going to be created in advance it's more efficient to use [new ListView].

Copy link
Contributor Author

@Hixie Hixie Jun 23, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  /// The `itemBuilder` should actually create the widget instances when called.
  /// Avoid using a builder that returns a previously-constructed widget; if the
  /// list view's children are created in advance, or all at once when the
  /// [ListView] itself is created, it is more efficient to use [new ListView].
  /// Even more efficient, however, is to create the instances on demand using
  /// this constructor's `itemBuilder` callback.

@HansMuller
Copy link
Contributor

LGTM

@Hixie
Copy link
Contributor Author

Hixie commented Jun 23, 2017

Thanks. I've pushed updates. Will land on green.

@Hixie Hixie merged commit ba520e7 into flutter:master Jun 23, 2017
@Hixie Hixie deleted the docs2 branch June 23, 2017 21:06
gspencergoog pushed a commit to gspencergoog/flutter that referenced this pull request Jul 1, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants