Add a note to developer pages to explicitly state use of cmake-lint but not the formatter. #440
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
…ut not the formatter.
jwallwork23
approved these changes
Oct 6, 2025
|
@jatkinson1000 LGTM! Thanks! |
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.
Should resolve #439
Makes it explicit that we expect code to obey
cmake-lintfromcmake-format, but do not apply the formatter as it is overly opinionated making line-length a target rather than a goal, thereby reducing readability (in our opinion).This should make it explicit in the docs following fair confusion in a community contribution PR.
This was originally discussed back in #204