-
Notifications
You must be signed in to change notification settings - Fork 478
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
Impose JuliaFormatter code style on the code #2338
Comments
Long-term, I'd say yes. @fredrikekre and I also discussed this at some point. But not sure we have the bandwidth to bikeshed a code style overhaul right now. It might be interesting to see what the diff would be with e.g. default JuliaFormatter settings. We definitely don't want unrelated major formatting changes in a feature or bugfix PR though. |
I have one in https://github.com/JuliaDocs/DocumenterCitations.jl/blob/master/.JuliaFormatter.toml (and DocumenterCitations has a CI step to check the code formatting, and The settings I’m using are pretty permissive, but Documenter might want to make some further tweaks to minimize the diff to the existing code. That’s pretty much the only drawback to adopting an automatic style: we’ll have one pretty big “reformat” commit. |
i just accidentally made a huge diff on my recent PR lmao |
I will try to restart and only add the changes with the formatting off tomorrow. need to sleep. |
This is JuMP's format: https://github.com/jump-dev/JuMP.jl/blob/master/.JuliaFormatter.toml It's great. We don't have arguments anymore. |
I have a question if the code of Documenter.jl has a JuliaFormatter configuration. I feel like it's needed since I don't want to annoy the maintainers of this project when contributing and also from future contributors. I just noticed this since I set up my Julia LSP to autoformat and caused a huge diff. Would anyone be interested on setting up at least their own JuliaFormatter config here so people will just use the config when formatting if they contribute?
The text was updated successfully, but these errors were encountered: