Use .lstk/config.toml for project-local config#149
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughThe project-local configuration file path changes from Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
gtsiolis
left a comment
There was a problem hiding this comment.
Go boring solutions! It's an elegant solution, compared to other ideas discussed.
anisaoshafi
left a comment
There was a problem hiding this comment.
LGTM, local test worked fine 🎉 thanks Silvio 🙏🏼
Motivation
Local config used
./lstk.tomlwhile all other config locations usedconfig.toml, which was confusing — users naturally createconfig.tomlin their project directory and it doesn't get picked up. This changes the local config to.lstk/config.tomlinside a conventional dotdir, making the filename consistent across all config locations.Changes
containers.gotopaths.gowhere they belong./lstk.tomlto./.lstk/config.tomlconfigFileNameconstant since all locations now useconfig.tomlInit()with Viper's built-inAddConfigPath/SetConfigNamesearchconfigSearchPaths()(full file paths) withconfigSearchDirs()(directories only)Tests
TestLocalConfigTakesPrecedenceupdated to use the new.lstk/config.tomlpathRelated