You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not very useful for panicking and can produce very odd and erroneous panic messages that are not consistent with the toString() of that object.
Currently observed with Scene2D's printing of its adjacency list, where the debugWordWrap treats spaces as places to break and does not realize that the string provided already has wraps.
Instead of treating \n as real new spaces, it instead treats it as a normal character.
Maybe forward this to Flutter's issues board?
The text was updated successfully, but these errors were encountered:
Oh im dum, in the debugWordWrap documentations they state:
The message should not contain newlines (\n, U+000A). Strings that may contain newlines should be String.split before being wrapped.
LOL. Yea it's just an implementation error due to my ignorance
Moving it up to triaged
exoad
added
triaged
Has been assessed for implementation.
pH
High Priority work order
and removed
in-triage
Being assesed for implementation.
labels
Mar 7, 2025
This is not very useful for panicking and can produce very odd and erroneous panic messages that are not consistent with the
toString()
of that object.Currently observed with
Scene2D
's printing of its adjacency list, where thedebugWordWrap
treats spaces as places to break and does not realize that the string provided already has wraps.Instead of treating
\n
as real new spaces, it instead treats it as a normal character.The text was updated successfully, but these errors were encountered: