fix: resolve config not loading from ~/.docscontext/ or config.yml#6
Merged
Conversation
The config loader only searched ~/.DocsContext/ (case-sensitive on Linux)
and restricted to .yaml extension via SetConfigType. Users creating
~/.docscontext/config.yml would silently fall back to ollama defaults.
- Add ~/.docscontext/ as primary config search path (lowercase, conventional)
- Remove SetConfigType("yaml") so Viper finds both .yaml and .yml
- Add slog warnings when no config file is found, showing searched paths
- Log which config file was loaded and the resolved LLM provider
https://claude.ai/code/session_011Ryet7uu9j6VyzNGmUuaaj
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.
No description provided.