Pieter Vanderwerff

@cpojer figured out my specific case :) but it would be great to check this in a less error prone way. Feel free to close if you dont think its...

Anything happen with this? Would love to do some testing around this API :)

No worries, thanks for looking into it @mattijsbliek.

I was having similar problems implementing if/else if/else breaks since if you use Labels to implement it will break in the wrong order, as per below: ``` if (x) {...

The list inserts the newline for the trailing "}" whereas the statement list is separated onto a newline via the Label within the list, like so: ``` [ "if ()...

> The only problem with the last suggestion (I think) is that you indent even if the if/else doesn't break. Not sure if this would work but may be able...

> `let x = if (something) {thenThis} else {thenThat};` Potentially should work if you output like this (apart from the inner indentation): ``` [ "let x = if (something) {",...

Looks like this has been fixed in Flow since this issue has been created as the astexplorer link is showing the elements after the first JSX element parsed as binary...

What you are describing is something we have done for a while with prettier, check out the `hermes-transform` package linked below (this is designed for Flow use cases so it's...

No the AST just needs to be compatible with what prettier expects, most parsers use the estree format. We use the Hermes parser which is not internal to prettier. The...