rebar3_format
rebar3_format copied to clipboard
AdRoll
Erlang Formatter for Rebar3
We need to check what changed in `erl_syntax` and `epp_dodger`, as usual, but we also need to add support for documentation attributes, sigils and triple-quoted-strings. Plus, `maybe` is enabled by...
**Describe the bug** The default formatter adds an empty line after an attribute if it finds a comment below it. That's an issue because EDoc uses comments after `-type`s to...
**Describe the bug** If the parser fails to correctly parse a form (e.g. due to macros), it will (silently) destroy the formatting of the function. This is very bad, as...
**Describe the bug** Given the following code ```erlang -module(format_bug). -export([foo/0]). -type foo() :: a_very_long_atom_which_almost_spans_the_entire_line_1 %% comment a | a_slightly_shorter_arom %% comment b | ok. -spec foo() -> foo(). foo() ->...
**Describe the bug** Trying to format a binary comprehension such as: ```erlang . ``` results in formatted code such as AFTER having produced an error for it: ```erlang . ```...
**Describe the bug** `-else.` gets formatted to `- else .` In `otp25`. In `otp24` it gets formatted to `-else.` **To Reproduce** Fomat the following code with `otp25`: ```erl -if(?OTP_RELEASE >=...
I believe it's important to prevent a module from being formatted with non-default features enabled in the current Erlang version, such as `maybe` in erlang26. This would be helpful in...
From Erlang/OTP 27, `maybe` is a default keyword, and optionally in 26 too. By default, the formatter changes the atom 'maybe' to maybe because previously it was a good thing...