Straight from the docs:

--check-formatted - check that the file is already formatted. This is useful in pre-commit hooks and CI scripts if you want to reject contributions with unformatted code. However, keep in mind, that the formatting output may differ between Elixir versions as improvements and fixes are applied to the formatter.

and

If any of the --check-* flags are given and a check fails, the formatted contents won’t be written to disk nor printed to stdout.

In the last bullet, I believe “Steam” should be “Stream.”

Working fine here too

Well done @doomspork - I am sure people are going to look forward to these updates

Disagreements about formatting are a thing of the past!

They aren’t as we still have the choice to not use the formatter.

I keep my stance, that shuffling comments (eg. comments on struct fields) and removing trailing commas is a bad idea. Also I’m not a friend of the uniform gap of a single line between different clauses of the same function and totally different functions.

Stream data and property testing will be joining Elixir core in a future release.

I’m looking forward into this!

I have fixed it. But a PR is definitely appreciated in the future, the repo is at GitHub - elixir-lang/elixir-lang.github.com: Website for Elixir.

Please open up an issue about the comment shuffling on struct fields, I don’t believe this particular behaviour is desired. The other complaints had their pros and cons discussed elsewhere, so I won’t rehash them there.

Ironically the code you wrote would be kept as is by the formatter. The issue is with do/end blocks which is where most disagree in regards to the placement of newlines (and the formatter chose to add a newline before and after the block).