Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request for API docs for custom multi-child layouts #5695

Closed
sethladd opened this issue Aug 31, 2016 · 3 comments · Fixed by #6980
Closed

Request for API docs for custom multi-child layouts #5695

sethladd opened this issue Aug 31, 2016 · 3 comments · Fixed by #6980
Assignees
Labels
framework flutter/packages/flutter repository. See also f: labels.

Comments

@sethladd
Copy link
Contributor

(Filing on behalf of a user.)

"Suggest that Flutter's API docs for custom multi-child layouts mention layout IDs."

@sethladd sethladd added framework flutter/packages/flutter repository. See also f: labels. ⚠ clear documentation labels Aug 31, 2016
@sethladd
Copy link
Contributor Author

cc @apwilson

@apwilson
Copy link
Contributor

Right: https://docs.flutter.io/flutter/material/CustomMultiChildLayout-class.html Doesn't mention that it's children should/must/could be LayoutIds.

@Hixie Hixie modified the milestone: Flutter 1.0 Sep 12, 2016
@abarth abarth self-assigned this Nov 22, 2016
abarth added a commit to abarth/flutter that referenced this issue Nov 22, 2016
@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
framework flutter/packages/flutter repository. See also f: labels.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants