chore(deps): update optnix dependency to v0.3.0#137
chore(deps): update optnix dependency to v0.3.0#137water-sucks merged 1 commit intonix-community:mainfrom
Conversation
WalkthroughUpgrades multiple dependencies including optnix v0.2 → v0.3, and refactors the interactive option UI configuration from flat single-scope to scope-based multi-scope architecture with loader callbacks. Updates Nix package vendorHash to reflect new dependencies. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant Caller
participant OptionTUI
participant Scope as Scope Loader
participant OptionSource
rect rgb(220, 240, 255)
Note over Caller,Scope: New scope-based initialization (v0.3)
Caller->>OptionTUI: NewOptionTUI(Scopes, SelectedScopeName, ...)
activate OptionTUI
OptionTUI->>Scope: Call Loader() when scope selected
activate Scope
Scope->>OptionSource: Load options
OptionSource-->>Scope: Return options
Scope-->>OptionTUI: Return loaded options
deactivate Scope
OptionTUI-->>Caller: UI ready
deactivate OptionTUI
end
rect rgb(240, 220, 220)
Note over Caller: Old flat initialization (v0.2)
Caller->>OptionTUI: NewOptionTUI(Options, ScopeName, Evaluator, ...)
end
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes
Pre-merge checks and finishing touches✅ Passed checks (5 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
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 |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
cmd/option/option.go (1)
192-215: Single-scope migration to optnix v0.3.0 looks correct; minor DRY nitThe new
Scopes+SelectedScopeNamewiring preserves the previous behavior (sameoptions,evaluator,minScore, debounce, and initial input) while adapting to the multi-scope API. To avoid future drift, you could put"nixos"in a smallconstand reuse it for bothNameandSelectedScopeName.Please sanity-check the interactive
nixos optionTUI (including<Esc>handling) against v0.3.0 docs / behavior to confirm there are no regressions from the upstream API change.go.mod (1)
100-100: Systemd fork replace is fine mechanically; consider documenting rationaleThe
replacefromgithub.com/coreos/go-systemd/v22togithub.com/water-sucks/go-systemd/v22at a pinned commit is syntactically correct and will transparently redirect existing imports.Given this affects low-level systemd integration, it’d be helpful to document briefly (e.g., in CONTRIBUTING or a module comment) why the fork is needed and how it tracks upstream, and to verify that all systemd-related usages still build and behave as expected with this replacement.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
go.sumis excluded by!**/*.sum
📒 Files selected for processing (3)
cmd/option/option.go(1 hunks)go.mod(2 hunks)nix/package.nix(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Build/Test
🔇 Additional comments (3)
nix/package.nix (1)
27-27: Vendor hash update is consistent with dependency changesThis looks like the expected
vendorHashrefresh after bumping Go dependencies; nothing stands out as incorrect here.go.mod (2)
9-27: Direct dependency bumps align with the optnix upgrade; confirm runtime compatibilityThe version bumps for
bubbletea,koanf/v2,cobra,pflag,optnix, and thegolang.org/x/*modules look consistent with adopting optnix v0.3.0 and newer TUI stacks. No obvious red flags from the versions alone; remaining risk is behavioral.Please ensure you’ve run the full test suite and exercised the interactive UIs (especially
nixos option) to catch any regressions from these library upgrades.
33-44: Transitive dependency refresh looks tidy; keep module files in syncThese indirect bumps (Charmbracelet stack, Chroma, Clippehouse, Goldmark,
golang.org/x/*, etc.) are what I’d expect from the direct upgrades. They look mechanically fine.Just confirm
go mod tidyproduces no further changes so future contributors don’t see unexpected diffs stemming from this refresh.Also applies to: 50-60, 67-67, 90-90, 92-95
This updates the
optnixdependency to v0.3.0 in order to bring in some fixes and enhancements tonixos option.This release brings support for multiple "scopes", which is not relevant in our case; as such, this PR just mimics the original functionality of only being able to browse a single list of options at one time.
Closes #136.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.