-
Notifications
You must be signed in to change notification settings - Fork 65
Initial configuration of Codee Fortran formatter with examples (src/*.F90)
#707
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
Initial configuration of Codee Fortran formatter with examples (src/*.F90)
#707
Conversation
dustinswales
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@climbfuji Thanks for incorporating the code formatter here!
I love the idea, we just need to decide on a few details and incorporate this into our workflows.
As a github action, running the formatter could be invoked either diagnostically (report format violations) or prognostically (fix format violations).
src/*.F90)src/*.F90)
|
@climbfuji This PR has merge conflicts that need to be resolved, then it can be merged |
On it! |
mkavulich
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Initial configuration of Codee Fortran formatter with examples (
src/*.F90).This PR adds an initial
.codee-formatconfiguration file for the free Codee Fortran formatter and a temporary scriptrun_codee_tmp.shto get started with the tool (note that the day-to-day usage will be much simpler than in the script). The PR also demonstrates the effect of the formatting rules for the four Fortran source files insrc/.The goal of this PR is to provide the necessary information to decide on the formatting rules we want to use. Once we have agreed on the format, we can update the
src/*.F90files as needed and merge this PR. The integration with GitHub actions and the simplified usage on the command line will come after that. In a 3rd PR, we will work on a tighter integration of the codee format config with the capgen Fortran write to make sure that the auto-generated code also complies with the formatting rules.The majority of the diffs are because NEPTUNE (and UFS) use two whitespaces as indentation, whereas the files in
src/currently use 3 whitespaces. We can change the codee config, but every space we save makes the lines shorter. To see the remaining differences, please select "Hide whitespaces" when looking at the files changed.User interface changes?: No
Working toward #703
Testing: No changes to the tests - GitHub actions CI tests passed
test removed:
unit tests:
system tests:
manual testing: