Skip to content
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

(In Progress) Update files to follow a more consistent style guide #98

Open
wants to merge 113 commits into
base: beta
Choose a base branch
from

Conversation

teejusb
Copy link
Collaborator

@teejusb teejusb commented Apr 4, 2023

Following the Google Style Guide found here: https://google.github.io/styleguide/cppguide.html

Using this PR to make sure that builds are still passing as I work my way through the files.

Variables will be updated as needed, but if they touch a lot of files I'll leave it for later.

Generally setting the clang format in VS Code to Google gets most of the way there.
image

{
  BasedOnStyle: Google,
  AlignAfterOpenBracket: AlwaysBreak,
  DerivePointerAlignment: false,
  PointerAlignment: Left,
  QualifierAlignment: Left,
  ReferenceAlignment: Left,
  InsertBraces: true
}

@teejusb teejusb added the draft label Apr 4, 2023
@teejusb teejusb force-pushed the style-guide branch 8 times, most recently from 9091ff6 to 1c4f0f7 Compare April 5, 2023 20:15
@florczakraf
Copy link
Contributor

Also leaving the link here for the reference: https://www.stefanjudis.com/today-i-learned/how-to-exclude-commits-from-git-blame/. It describes a way of ignoring reformatting commits in git blame

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants