Open sdankel opened 2 months ago
My two piece on this would be not to allow it. This is purely a personal choice so nothing concrete behind it but even if someday we have the bandwidth to do so, I think we still shouldn't do it. I feel like formatter wise go made the correct choice over rust.
Also I believe that being a smart contract development language, conceptually gives us an extra opportunity to say that we are opinionated about standards, this can (and imo should) include the way sway programs supposed to look.
My problem with rustfmt is that the lack of standard look, rust itself enforces some strict rules on how you structure your code, the formatter should have followed a similar philosophy of being opinionated. Also I see bunch of weird diffs in different rust repos, due to different rustfmt configs
We decided as a team we do not want the formatter to be configurable. The next step is to remove the configuration code that currently exists in the formatter but isn't exposed in swayfmt/src/config
.
Swayfmt is meant to be configurable. The task here is to:
swayfmt.toml
The main reason it's not currently supported is that our small team hasn't had bandwidth to properly tests the options that are implemented.
The default swayfmt.toml: