How to prevent the compiler on js to put if-else in one line

[Rafael Oliveira]

The compiler on js takes a code like this:

if (a == 0)

      trace("aaa");

else

      trace("bbb");

and transform in this:

if(a == 0) console.log("aaa"); else console.log("bbb");

this is hard to debug because I can't put a breakpoint on the else because everything is on the same line.

is there a compiler flag to respect the lines in the source?

[Benjamin Dubois]

Is there a reason you are not using source mapping so that you can put the breakpoint in your haxe code ?

--
To post to this group haxe...@googlegroups.com
http://groups.google.com/group/haxelang?hl=en
---
You received this message because you are subscribed to the Google Groups "Haxe" group.
For more options, visit https://groups.google.com/d/optout.

[Rafael Oliveira]

With source mapping I can't see the values of all the variables, same variables Google Chrome don't show the value (maybe because the implementation is using a different code). And the if-else in the same line prevent me to set a breakpoint on the else. If I click in the line with the else, Chrome put the breakpoint some lines above the else.

[Raoul Duke]

> implementation is using a different code). And the if-else in the same line
> prevent me to set a breakpoint on the else. If I click in the line with the
> else, Chrome put the breakpoint some lines above the else.

agreed, i think that sucks.

even if sourcemaps did not have some trouble, i think it is still
better to generate code that is as debuggable as possible from the
get-go, rather than having to make people jump through more hoops.

[Philippe Elsass]

+1 I prefer working without source mapping and I'm often annoyed by these one liners.

[michael solomon]

Why not use "debugger" js keyword?
http://try.haxe.org/#07804

[Rafael Oliveira]

Works, but is not the best solution. I opened a issue:

https://github.com/HaxeFoundation/haxe/issues/4542

[Juraj Kirchheim]

Can't you simply run your Haxe output through a JS beautifier/formatter of your choice?

--

[Raoul Duke]

> Can't you simply run your Haxe output through a JS beautifier/formatter of
> your choice?

Sounds like quite possibly a perfectly reasonable work around. Good idea.

In the long run, it would still be really nice if Haxe's output was
written with debugability in mind from the get-go. Ideally. Some day.
In a perfect world. In the future. :-)

[Rafael Oliveira]

I tested these options, but none of them worked. does anyone know other options?

https://github.com/beautify-web/js-beautify

https://github.com/mishoo/UglifyJS/ (with --beautify)

[Zach Lym]

Can't you simply run your Haxe output through a JS beautifier/formatter of your choice? 

FWIW, there is support for chaining together map outputs, but this would break it by default.

So it's still a PITA.