Open lucasdauto opened 6 years ago
Thanks for the report @lucasdauto! We'll look into this next week (:
This is odd. From what I can tell, text
is guaranteed to be a string. In fact, we even check for a falsy value or empty string and ensue it's a non empty string here: https://github.com/facebook-atom/atom-ide-ui/blob/master/modules/atom-ide-ui/pkg/atom-ide-console/lib/ui/RecordView.js#L94
I guess that means that text
must be both truthy and not a string. I don't immediately see how that could be the case.
This is odd. From what I can tell,
text
is guaranteed to be a string. In fact, we even check for a falsy value or empty string and ensue it's a non empty string here: https://github.com/facebook-atom/atom-ide-ui/blob/master/modules/atom-ide-ui/pkg/atom-ide-console/lib/ui/RecordView.js#L94I guess that means that
text
must be both truthy and not a string. I don't immediately see how that could be the case.
I ran into this issue as well. I caused it by calling console.error(anExceptionObject)
(pseudocode), and seeing how it'd come out. anExceptionObject
would be truthy and not a string. I should have done console.error(anExceptionObject.toString()
. log
and friends expect a string input. This was mostly caused on my end by not looking at the expected types, but the note about only allowing string or falsey input wasn't in the formal documentation.
[Enter steps to reproduce:]
Atom: 1.31.2 x64 Electron: 2.0.7 OS: Unknown Windows version Thrown From: atom-ide-ui package 0.13.0
Stack Trace
Uncaught TypeError: text.slice is not a function
Commands
Non-Core Packages