Skip to content

Follow-ups of #736: plugin updates, the path.mode default and vfox config #737

Closed

Description

@linghengqian

#736 is merged (feb6092) and released in v1.1.0, together with #738 (baseline is now the default path.mode) and #739 (vfox config writes only the key it sets). It added vfox link, vfox doctor, vfox alias, installation receipts, the optional Fingerprint and Detect hooks, PLUGIN.shadowHints and the path.mode setting.

This issue collects what is left, so that each item can be picked up, discussed or dropped on its own. #736 closed #706 and #669. Update 2026-11-10, verified against main at v1.1.0 (3682fe8) plus the plugin releases of today (gradle v0.1.3, java v0.6.6, nodejs v0.5.6, flutter v0.2.6, golang v0.4.3) and the template PR merge (version-fox/vfox-plugin-template#12): #670 and #359 are closed (aliases are in, see 1); #337 is closed COMPLETED by the baseline default and only #732 stays open, pending a Windows re-test with baseline as the default (see 1); 3 and 4 are done; in 2, flutter/nodejs/java/template are done (template release pending in version-fox/vfox-plugin-template#13); 5 is still open.

1. Release

2. Plugins

The new hooks are optional. Older vfox versions (checked: 0.6.0, 1.0.0 and 1.0.13) never load a hook file they do not know and skip metadata fields they do not know, so a plugin can add them without raising minRuntimeVersion. For plugin authors: Fingerprint, Detect and shadowHints.

Verified 2026-11-10: flutter, nodejs, java and template are done (see below; template release pending in version-fox/vfox-plugin-template#13).

Per-plugin issues can be opened in the plugin repositories and linked here. Beyond the four above, also released today: vfox-golang v0.4.3 (version-fox/vfox-golang#26: Detect + shadowHints) and vfox-gradle v0.1.3 (version-fox/vfox-gradle#8: Detect + shadowHints + Fingerprint + parse_legacy_file). Python Detect is the obvious remaining candidate.

3. Change the default of path.mode to baseline

Done in #738, released in v1.1.0. config.DefaultPathMode is baseline; EmptyPath, both fallbacks of EffectiveMode, and the starting mode of pathPolicy() use it. Docs (EN + zh-hans), internal/sdk/check.go hints, and the AGENTS.md bullet are updated.

  • Decide the release, and whether an earlier release should warn first, for instance with a notice from vfox doctor while path.mode is not set explicitly. Decided: shipped directly in v1.1.0 (feat(config): make baseline the default path.mode #738, dfd5782, 2026-11-07), no warning release.
  • Code: EmptyPath in internal/config/path.go, the two fallbacks in EffectiveMode (they return legacy for an empty or an unknown value; decide whether a typo should land on the new default) and the starting mode in pathPolicy() in internal/env/pathpolicy.go. A throw-away flip of these fails 11 tests in cmd/commands, internal/config, internal/env and internal/sdk, which assert the old default. Done: typo/empty fall back to the new default (DefaultPathMode), tests updated in feat(config): make baseline the default path.mode #738.
  • Docs, English and zh-hans: drop the announcements and the "set baseline" step in docs/guides/quick-start.md and both READMEs, update docs/guides/configuration.md and docs/guides/faq.md, and say how to keep the old behavior (vfox config path.mode legacy). Also the bullet in AGENTS.md that says legacy stays the default. Done in feat(config): make baseline the default path.mode #738 (quick-start no longer mentions path.mode; configuration guide documents baseline (the default) and vfox config path.mode legacy; AGENTS.md says baseline, the default).
  • The hints of the path.shadowed finding in internal/sdk/check.go suggest vfox config path.mode baseline. Reword them. Done: hints now distinguish legacy vs post-activation additions / missing baseline.
  • Release notes: say it first, with the one-line way back. Done in the sense that feat(config): make baseline the default path.mode #738 is the first feature entry of v1.1.0; the one-line way back (vfox config path.mode legacy) lives in the configuration guide, not in the release notes.

To keep in mind: a shell that was started before the upgrade has no recorded baseline and keeps behaving like legacy until it is restarted. A directory that has to stay in front of vfox's can be listed in path.preserve. vfox doctor says what shadows a command and why.

4. vfox config should write only the key it sets

Done in #739, released in v1.1.0.

Before #739, vfox config <key> <value> loaded the merged shared and user configuration and saved all of it into the user's config.yaml. The user's file then held a copy of every section, the shared aliases included, and since a section that the user's file declares replaces the shared one, a later change of the shared configuration no longer applied. --unset wrote the default value instead of removing the key. vfox alias already edited only its own key (config.AliasFile).

5. Smaller items

Verified 2026-11-10: both still open.

  • CI has no Nushell, so the generated vfox.nu is only checked as text. Add a job that installs Nushell, sources the script and checks that vfox env sees __VFOX_ORIG_PATH. It was checked by hand with Nushell 0.116.1 for feat: link existing SDKs, add vfox doctor, aliases and path.mode #736.
  • The CLI-level tests in cmd/commands (cliFixture in cli_test.go) skip on Windows, where only the unit tests and the E2E workflow run. Make the fixture work there, so that the junction, .cmd and PATH separator cases are covered end to end as well.

6. Open questions from the description of #736

Shipped in v1.1.0, so decided by release unless somebody reopens them:

Activity

  1. self-assigned this
    on Oct 22, 2026
  2. linghengqian commented on Oct 22, 2026

    @linghengqian
    MemberAuthor

    I am working on the current issue.

  3. linghengqian commented on Nov 10, 2026

    @linghengqian
    MemberAuthor

    Update 2026-11-10, verified against main at v1.1.0 (3682fe8):

    Done since the issue was opened:

    Still open:

    The issue description is updated accordingly (1/3/4/6 marked done, 2/5 left open).

  4. linghengqian commented on Nov 10, 2026

    @linghengqian
    MemberAuthor

    Update 2026-11-10, after today's plugin releases (verified against each repo's main):

    Done since the last update:

    Still open:

    The issue description is updated accordingly (§1/#337, §2 plugin bullets, §6 consumer note).

  5. added this to the 1.1.1 milestone on Nov 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

planpossible things to dopluginPlugin-related issues

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions