Skip to content

Conversation

@Hixie
Copy link
Contributor

@Hixie Hixie commented Jan 6, 2017

LayoutCallback passes constraints to the callback, but the constraints
object has a different type for different subclasses. This lets you
call invokeLayoutCallback() with a specific type to verify that
everything is working as expected.

Other changes:

Slightly improve the error reporting in RenderObject.

Allow toStringShallow on RenderObject to have its separator configured.

LayoutCallback passes constraints to the callback, but the constraints
object has a different type for different subclasses. This lets you
call invokeLayoutCallback() with a specific type to verify that
everything is working as expected.

Other changes:

Slightly improve the error reporting in RenderObject.

Allow toStringShallow on RenderObject to have its separator configured.

if (callback != null)
invokeLayoutCallback(callback);
invokeLayoutCallback/*<BoxConstraints>*/(callback);
Copy link
Contributor

Choose a reason for hiding this comment

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

I thought we could use real generic functions now. I know you haven't landed the uber conversions patch, but maybe we should start using the real syntax for new instances?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Needs a dart roll still.

@abarth
Copy link
Contributor

abarth commented Jan 6, 2017

LGTM

@Hixie Hixie merged commit b0e8520 into flutter:master Jan 6, 2017
@Hixie Hixie deleted the layoutCallback branch January 6, 2017 06:12
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 14, 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