Fix formatting for Tempo Sync Knob Model#8449
Open
JJCUBER wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I have been going through and incrementally updating the formatting of files to better match the Coding Conventions. I am starting with files that haven't been touched in years to both serve as a litmus test and as a way to avoid causing (hopefully) any conflicts for prs being considered leading up to alpha.2. I am currently updating one header+impl pair per pr, but I can change the level of granularity if needed.
I tried my best to adhere to the aforementioned Coding Conventions, but if there is anything I should modify (and/or should keep in mind for future files I convert), please let me know.