René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Resolve JSON.stringify vs prettier conflict in generated src/version.ts","articleBody":"Follow-up to #289.\n\n`scripts/generate-version.ts` emits string literals via `JSON.stringify(...)` as part of the PR's defense-in-depth hardening. That produces double-quoted strings, which prettier rejects in `src/version.ts`.\n\n## Current workaround\n\n`src/version.ts` was added to the eslint `ignores` list (commit on the rebased PR branch). The file is `.gitignore`d and regenerated on every build, so the ignore is correct in practice.\n\n## Open risk\n\nIf anyone later runs prettier directly on `src/version.ts`, or wires the generated file into a non-eslint format check (CI step, pre-commit hook, etc.), the format check will fail. The workaround is invisible to non-eslint tooling.\n\n## Options\n\n1. **Keep `JSON.stringify` and document the eslint-only carve-out** — current state. Defense-in-depth preserved.\n2. **Switch to single-quoted output** in `scripts/generate-version.ts`. Safe because `validateVersion` constrains the emitted strings to a regex that excludes `'`, `\\\\`, and other shell-meaningful characters. Removes the prettier carve-out.\n3. **Run prettier on the generated file as a post-step** in `scripts/generate-version.ts` before writing. More machinery, no defense-in-depth loss.\n\nOption (2) is the cheapest if the regex is the source of truth, but it depends on `VERSION_REGEX` actually constraining the values (see #368 for the related extraction work).","author":{"url":"https://github.com/cameroncooke","@type":"Person","name":"cameroncooke"},"datePublished":"2026-04-26T21:13:54.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/369/XcodeBuildMCP/issues/369"}