docs(config): document extra_extensions values and skip behavior - #487
Merged
DeusData merged 1 commit intoJul 4, 2026
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
The README's "Custom File Extensions" section showed a single example key and stated that unknown language values are "silently skipped". Issue #359 asks what other config-file options exist and where they are documented. - Clarify that `extra_extensions` is the only key the JSON config files accept. - List the accepted, case-insensitive language names (and aliases) so users know which values are valid. - Document the "extension must start with ." rule. - Correct the behavior note: invalid entries are skipped with a warning logged to stderr (the parser calls cbm_log_warn), not silently. Closes #359 Signed-off-by: Johnson K C <Johnsonkc201@gmail.com>
Copy link
Copy Markdown
Contributor
Author
|
Friendly ping on this one — it is a small docs-only change and all CI checks are green. Happy to adjust anything if needed before merge. |
Sorry, something went wrong.
Copy link
Copy Markdown
Owner
|
Huge thanks for opening this PR and for the work you put into it. The maintainer shop is currently full, so this may sit for a bit before it gets a proper review. We will come back to this as soon as possible with real feedback; I wanted to make sure it did not sit unacknowledged in the meantime. |
Sorry, something went wrong.
This was referenced Jul 21, 2026
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
2 participants
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.
Closes #359.
The README's Custom File Extensions section previously showed a single example key and stated unknown language values are "silently skipped". #359 asks which other config-file options exist and where they're documented.
This clarifies the config-file surface and fixes an inaccuracy:
Docs only — no code changes. Verified against main (e599df1).