Haxe 3.2.0-rc.2 Browser.window.console.log() Too many arguments

[Chris Anderson]

appreciate all the work you guys have put into the 3.2 release.  have a quick question.  it's not a show stopper but was a nice to have.  in previous versions i could use console log/warn/etc to log out entire objects (as opposed to trace which wouldn't trace out the entire object).  

Browser.window.console.log('onPolymerResponse() event: ', event);

the comma was respected and allowed chrome's console to render an inspectable object.  after 3.2 rc2 any call to console.log() with a comma throws and error:

Too many arguments

is there a workaround that i'm unaware of?

[Chris Anderson]

this might be good enough for me:

Browser.window.console.log({'onPolymerResponse() event: ': event});

[Chris Anderson]

even better i could really use trace (brain was turned off):

trace({'onPolymerResponse() event: ': event});

and --no-traces can assist me better.

[Dan Korostelev]

Actually, this is a good catch! HTML externs are generated from WebIDL files that have notion of "rest" arguments that are now supported for externs by Haxe. So it should allow multiple arguments.

пятница, 20 марта 2015 г., 17:25:02 UTC+3 пользователь Chris Anderson написал: