Skip to content

feat: uteke.toml config with layered resolution#68

Merged
ajianaz merged 1 commit into
developfrom
feat/uteke-toml-config
May 29, 2026
Merged

feat: uteke.toml config with layered resolution#68
ajianaz merged 1 commit into
developfrom
feat/uteke-toml-config

Conversation

@ajianaz

@ajianaz ajianaz commented May 29, 2026

Copy link
Copy Markdown
Collaborator

Summary

Closes #48

Changes

  • Create crates/uteke-cli/src/config.rs β€” full Config struct with 5 sections:

    • [store] β€” path, namespace
    • [embedding] β€” model, max_seq_length
    • [tier] β€” hot_days, warm_days, hot_boost
    • [logging] β€” level, file
    • [aging] β€” enabled, max_age_days, max_cold_count
  • Modify crates/uteke-cli/src/main.rs β€” add mod config;, remove old Config struct, wire new config

  • Layered config resolution: CLI args > project .uteke/uteke.toml > global ~/.uteke/uteke.toml > defaults

  • Legacy migration: config.toml β†’ uteke.toml with .bak backup

  • 8 unit tests: defaults, full parse, partial parse, merge, nonexistent file, tilde expansion, old format migration

Verification

  • βœ… cargo check β€” clean
  • βœ… cargo clippy β€” no warnings
  • βœ… cargo test β€” 22 passed (15 core + 7 config)
  • βœ… cargo fmt β€” clean

…al > defaults)

- Create config.rs with full Config struct (store, embedding, tier, logging, aging)
- Layered resolution: CLI args > .uteke/uteke.toml > ~/.uteke/uteke.toml > defaults
- Migrate legacy config.toml β†’ uteke.toml with backup
- Expand tilde paths via Config::expand_tilde
- 8 unit tests covering defaults, parsing, merge, migration
- Remove old Config struct and write_default_config from main.rs

Closes #48
@coderabbitai

coderabbitai Bot commented May 29, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@ajianaz, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 30 minutes and 59 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

βŒ› How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
βš™οΈ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e3c68757-058b-4b6c-b7b9-08a2a96f3f55

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 30ef4e7 and c8b49e2.

πŸ“’ Files selected for processing (2)
  • crates/uteke-cli/src/config.rs
  • crates/uteke-cli/src/main.rs
✨ Finishing Touches
πŸ§ͺ Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/uteke-toml-config

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.

❀️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@ajianaz
ajianaz merged commit b92a7b1 into develop May 29, 2026
7 checks passed
@ajianaz
ajianaz deleted the feat/uteke-toml-config branch May 30, 2026 04:55
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.

feat: configuration file (uteke.toml)

1 participant