refactor/harness: name the repeated mcp.json literal

pti commented

2026-10-19 22:44:10 +02:00

Owner

Part of the SonarQube cleanup in #73, the harness slice. One go:S1192 finding. The mcp.json filename the Pi and omp harness descriptors build their project and global config paths from, four filepath.Join sites, becomes mcpConfigFile. Claude's .mcp.json is a different string and stays as is. Every resulting path is byte-identical, harness and cmd tests untouched and passing. 🤖 Generated with Claude Code

pti added 1 commit

2026-10-19 22:44:10 +02:00

refactor(harness): name the repeated mcp.json literal

Lint / lint (pull_request) Successful in 1m7s

Details

Lint / sonarqube (pull_request) Has been skipped

Details

3d0a6831d2

The Pi and omp renderers each spelled the "mcp.json" filename twice, once
for the project path and once for the global one. Name it once as
mcpConfigFile so go:S1192 stops flagging the repeated literal. Every
resulting path is byte-identical; behaviour is unchanged.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

pti merged commit f831343684 into main

2026-10-19 22:47:08 +02:00

pti deleted branch refactor/literals-harness

2026-10-19 22:47:08 +02:00

pti referenced this pull request from a commit

2026-10-19 22:47:10 +02:00

Merge pull request 'refactor/harness: name the repeated mcp.json literal' (#100) from refactor/literals-harness into main

Rows
Columns

refactor/harness: name the repeated mcp.json literal #100