Skip to content

docs(config): document extra_extensions values and skip behavior#487

Open
JOhnsonKC201 wants to merge 1 commit into
DeusData:mainfrom
JOhnsonKC201:docs/extra-extensions-reference
Open

docs(config): document extra_extensions values and skip behavior#487
JOhnsonKC201 wants to merge 1 commit into
DeusData:mainfrom
JOhnsonKC201:docs/extra-extensions-reference

Conversation

@JOhnsonKC201

Copy link
Copy Markdown

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:

  • States that extra_extensions is the only key the JSON config files (.codebase-memory.json / config.json) accept, and points to the Environment Variables table and config subcommand for other tunables.
  • Lists the accepted, case-insensitive language names (and aliases) from LANG_NAME_TABLE in src/discover/userconfig.c, so users know which values are valid.
  • Documents the "extension must start with ." rule.
  • Corrects the behavior note: invalid entries are skipped with a warning logged to stderr (parse_extra_extensions calls cbm_log_warn("userconfig.unknown_lang", …)), not silently.

Docs only — no code changes. Verified against main (e599df1).

The README's "Custom File Extensions" section showed a single example key
and stated that unknown language values are "silently skipped". Issue DeusData#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 DeusData#359

Signed-off-by: Johnson K C <Johnsonkc201@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Where can I find docs for configuration files?

1 participant