Merged
Conversation
Owner
|
Thanks so much! Looks great. |
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
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.
Hello,
I added my .clang-format mixed with nuklear_console .clang-format changes.
I also tried to close as possible to raylib CONVENTIONS:
The Name convention can be forced with .clang-tidy readability-identifier-naming.*.
Control flow statements always are followed by a spaceUse more common~~/"modern"~~ C++ style, seeBraceWrappingI try to make the style as close as possible to raylib AND modern C++, @RobLoach pls verify this style and use it from now on, make changes as you wishes ... after that I would recommend formatting the code before/after mergen an PR.
(Use the formatted files as a "preview")
For convince, I added a CMake command
format, I personally using Format.cmake, making a simple command does the job (I'm sure there are better solutions)