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
Fix a TextSpan test #135187
Fix a TextSpan test #135187
Conversation
final List<ui.TextBox> boxes = <ui.TextBox>[ | ||
for (int i = 0; i < text.length; ++i) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why hardcode to be 4? Should it use textSpan.toPlainText instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The span tree looks pretty straightforward and we use equals(4) below anyway. If you prefer toPlainText
I can switch to that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, let's switch back to use toPlainText. If this hardcode to 4 the below equals(4)
expect is obsolete I think.
c6ebd4b
to
bb592ae
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
`TextSpan.toStringDeep()` returns a string that contains a lengthy diagnostic message instead of the plain string.
TextSpan.toStringDeep()
returns a string that contains a lengthy diagnostic message instead of the plain string.Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.