Format code with Runic #167
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When working on the recent PRs, and in particular the refactoring, it was sometimes a bit difficult to know (or rather guess) how to format code in a way that is seemingly consistent with the existing code.
Hence in this PR I propose to adopt a formatting style. I like Runic, but of course JuliaFormatter could be used as well.
I suggest to exclude the formatting commit (on the master branch) from the git blame history by adding a
.git-blame-ignore-revsfile in a follow-up PR: https://github.com/fredrikekre/Runic.jl?tab=readme-ov-file#ignore-formatting-commits-in-git-blame