fix(config): apply token substitution for OPENCODE_CONFIG_CONTENT #13226
+164
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
When config is provided via the
OPENCODE_CONFIG_CONTENTenvironment variable, token substitution ({env:VAR},{file:path}) was not being applied because the inline JSON was merged directly viaJSON.parse()instead of going through theload()pipeline that handles substitution.This change routes inline config content through
load()so that all token references are resolved consistently with file-based configs.Changes
packages/opencode/src/config/config.ts: ParseOPENCODE_CONFIG_CONTENTwith JSONC, inject$schemaif missing, and pass throughload()for token substitutionpackages/opencode/test/config/config.test.ts: Add 6 tests covering{env:VAR}substitution,{file:path}substitution, missing file errors, precedence over project config, malformed JSON rejection, and no disk artifact creationTest command
bun test packages/opencode/test/config/config.test.tsFixes #13219