-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cosmos code formatting standard #15546
Comments
I may abandon this idea: |
It would be great to see a diff of the current config compared to this and a small explanation of what this adds. |
@julienrbrt -- I think this will be a lot smaller in the end. It got excessive, to the point of breaking stuff. |
Thanks, it would be clearer if the default settings were not specified in the |
closing this as the current linter is enough |
The idea behind #15528 was to apply a very strict set of linters to enhance consistency over the SDK -- and then to use that standard outside of the SDK, too.
@tac0turtle yep, it was an obscenely large PR.
Here's my thoughts on what a standard could look like:
The key idea here is to make it more difficult for downstream teams to ship fairly chaotic code, by adopting standards that are as tight as possible.
The precise form that it takes, I'm quite open to ideas on.
Consider:
The idea would be to bring this to as many chains as possible, making maintainership easier. I'd rather have golangci-lint / revive take over as much of the task around layout / formatting as possible, so that chains don't diverge too much stylistically -- unless they'd like to do so, by disabling the linter, or changing its settings.
Definitely interested in others' opinions here :)
The text was updated successfully, but these errors were encountered: