fprettify

[sseraj]

Purpose

Formatting the Fortran code with fprettify

Expected time until merged

1 week

Type of change

• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (non-backwards-compatible fix or feature)
• [x] Code style update (formatting, renaming)
• [ ] Refactoring (no functional changes, no API changes)
• [ ] Documentation update
• [ ] Maintenance update
• [ ] Other (please describe)

Testing

Current test pass

Checklist

• [x] I have run flake8 and black to make sure the code adheres to PEP-8 and is consistently formatted
• [x] I have run unit and regression tests which pass locally with my changes
• [ ] I have added new tests that prove my fix is effective or that my feature works
• [ ] I have added necessary documentation

[sseraj]

Verified that the fprettify check fails without formatting and outputs which files need to be formatted

[codecov[bot]]

Codecov Report

Merging #44 (93c3fd8) into main (85281e8) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #44   +/-   ##
=======================================
  Coverage   60.51%   60.51%           
=======================================
  Files           5        5           
  Lines        1616     1616           
=======================================
  Hits          978      978           
  Misses        638      638           

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

[akleb]

Why not stick with the two space tab?

[sseraj]

Previously, we had an initial 2 space tab and then 3 space tabs after that. We decided to use a 4 space tab to be consistent with our Python formatting.

[sseraj]

Verified that a single file failure also fails the job