Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the flexibility of vfox backend plugins by enabling the transmission of custom, user-defined options from configuration files directly into the plugin's execution context. This allows for more dynamic and tailored behavior within individual plugins, supporting advanced use cases that require specific build or environment parameters without hardcoding them.

Highlights

• Custom Options for Backend Plugins: Introduced the ability to pass custom options from the toml configuration directly to vfox backend plugins. These options are now accessible within Lua plugin scripts via ctx.options.
• Context Struct Updates: The BackendExecEnvContext and BackendInstallContext structs were extended to include an options field, allowing custom data to be carried through the plugin execution lifecycle.
• Core Logic Integration: The core vfox logic was updated to accept and propagate these custom options to the backend plugin methods during both installation and environment execution.
• Documentation Updates: The backend-plugin-development.md documentation was updated to guide plugin developers on how to access and utilize the new ctx.options within their Lua scripts.

Greptile Summary

Adds custom options passthrough to vfox backend plugins, enabling plugin authors to access configuration options like build_cores from their Lua code via ctx.options. The implementation consistently adds an options field (IndexMap<String, String>) to both BackendInstallContext and BackendExecEnvContext, properly serializes them to Lua tables, and updates the documentation with usage examples.

Changes:

• Added options field to backend context structs in vfox crate
• Updated backend_install and backend_exec_env method signatures to accept options parameter
• Modified VfoxBackend to pass opts.opts.clone() when calling backend methods
• Updated backend plugin documentation with examples showing how to access custom options in Lua

The implementation follows existing patterns in the codebase and maintains backwards compatibility.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes are straightforward and follow existing patterns consistently across all affected files. The implementation properly handles serialization, maintains backwards compatibility (empty options map for plugins not using them), and includes clear documentation. No critical issues or logic errors were identified.
• No files require special attention

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Config as mise.toml Config
    participant Backend as VfoxBackend
    participant VfoxAPI as Vfox API
    participant Context as Backend Context
    participant Lua as Lua Plugin
    
    Config->>Backend: Tool with options<br/>{version: "latest", build_cores: 22}
    Backend->>Backend: Get tv.request.options()
    Backend->>VfoxAPI: backend_install/backend_exec_env<br/>(pathname, tool, version, paths, opts.opts.clone())
    VfoxAPI->>Context: Create BackendInstallContext/<br/>BackendExecEnvContext with options
    Context->>Context: IntoLua: serialize options<br/>using lua.to_value(&self.options)
    Context->>Lua: Pass ctx with options table
    Lua->>Lua: Access via ctx.options.build_cores

_{Last reviewed commit: b2d4405}