Skip to content

fix: read defaultLevel from pluginConfigs in settings.json#192

Open
gian-bytecode wants to merge 1 commit intoJuliusBrussee:mainfrom
gian-bytecode:fix/plugin-config-default-level
Open

fix: read defaultLevel from pluginConfigs in settings.json#192
gian-bytecode wants to merge 1 commit intoJuliusBrussee:mainfrom
gian-bytecode:fix/plugin-config-default-level

Conversation

@gian-bytecode
Copy link
Copy Markdown

getDefaultMode() skipped pluginConfigs.'caveman@caveman'.options.defaultLevel entirely, falling back to hardcoded 'full'. Users had to /caveman ultra every session despite configuring defaultLevel in settings.json.

Resolution order is now:

  1. CAVEMAN_DEFAULT_MODE env var
  2. pluginConfigs.'caveman@caveman'.options.defaultLevel in settings.json
  3. ~/.config/caveman/config.json defaultMode
  4. Hardcoded 'full'

Fixes #189

getDefaultMode() skipped pluginConfigs.'caveman@caveman'.options.defaultLevel
entirely, falling back to hardcoded 'full'. Users had to /caveman ultra
every session despite configuring defaultLevel in settings.json.

Resolution order is now:
1. CAVEMAN_DEFAULT_MODE env var
2. pluginConfigs.'caveman@caveman'.options.defaultLevel in settings.json
3. ~/.config/caveman/config.json defaultMode
4. Hardcoded 'full'

Fixes JuliusBrussee#189
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.

[Bug]: caveman plugin ignores defaultLevel config on session startup

1 participant