Document hierarchical lint configuration#1301
Merged
SeanTAllen merged 1 commit intomainfrom Apr 5, 2026
Merged
Conversation
ponyc PR #5135 adds subdirectory .pony-lint.json support. Update the linting docs to cover subdirectory overrides, category-cleaning merge semantics, and malformed config handling. Also update the exit code table to include malformed configs.
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.
Update the linting documentation to cover hierarchical
.pony-lint.jsonsupport being added in ponylang/ponyc#5135.--disabletakes precedence over all config files including subdirectory overridesParked review item: The Completeness reviewer flagged that the interaction between
--config(explicit config path) and the hierarchy root anchoring isn't documented. This is an edge case — when someone passes--config /some/path/.pony-lint.json, subdirectory configs are resolved relative to that file's directory. Didn't include it because it adds complexity for an uncommon scenario, but worth considering.