Style(#44): air formatting of functions

[andybeet]

Your commits explain the who, what, where and when of these changes. Your code shows the how. You do not need to reiterate this. This PR should complete the big picture by telling the why.

Justification

Formatting repo to maintain conformity to a style guide. The included workflow will check for this conformity. The toml sets the guidelines

fixes #44

Types of changes

What types of changes does your code introduce? Put an x in the boxes that apply. This will inform version updates

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other change (if none of the other choices apply)

Reviewer instructions:

Check to make sure the workflow (format-check) passed. No changes to code functionality were made. Just a style change. No need to run code

Formatting

This repo contains an air.toml file that automatically formats code to a set of standards.
It is preferred that contributors and reviewers install the air formatting tool.