You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed a weird behaviour when commenting a case with multiple patterns and pointed it out to @giacomocavalieri to assure it wasn't intended behaviour.
Here's an example:
fnfoo(a:Int,b:Int)->Bool{casea,b{// a very long comment a very long comment a very long comment a very long comment1,2->True_,_->False}}
After the formatting, the code above becomes the following:
fnfoo(a:Int,b:Int)->Bool{casea,b{// a very long comment a very long comment a very long comment a very long comment1,2->True_,_->False}}
Such behaviour happens only when the comment is quite long (i suppose > 80 characters?) and in case of a shorter one the formatter works as expected.
fnfoo(a:Int,b:Int)->Bool{casea,b{// a not quite long comment1,2->True_,_->False}}
Version info
OS: Windows 11
gleam 1.1.0
rebar 3.22.1 on Erlang/OTP 25 Erts 13.2.2.2
I noticed a weird behaviour when commenting a case with multiple patterns and pointed it out to @giacomocavalieri to assure it wasn't intended behaviour.
Here's an example:
After the formatting, the code above becomes the following:
Such behaviour happens only when the comment is quite long (i suppose > 80 characters?) and in case of a shorter one the formatter works as expected.
Version info
OS: Windows 11
gleam 1.1.0
rebar 3.22.1 on Erlang/OTP 25 Erts 13.2.2.2
Logs
link to pastebin
The text was updated successfully, but these errors were encountered: