[gonzaloriestra]

WHY are these changes introduced?

Theme Check JSON uses zero-based positions while terminal output and common source-reading tools use one-based line numbers. Matching those conventions avoids conversions for agents and other consumers. Slack discussion.

WHAT is this pull request doing?

Report one-based startRow, startColumn, endRow, and endColumn through both --json and --output=json, and require positive integers in the result schema. Update the shared JSON convention and generated help.

This is a breaking change: consumers must stop adding 1 to these positions.

How to manually test your changes?

Use a theme with a known Theme Check offense and run:

pnpm shopify theme check --path /path/to/theme --output=text
pnpm shopify theme check --path /path/to/theme --json
pnpm shopify theme check --path /path/to/theme --output=json

Compare the JSON positions with the source in your editor and the line displayed in the text snippet. The first line and column are 1 in JSON; both JSON flags should report the same positions.

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact

[gonzaloriestra]

/snapit

[github-actions]

🫰✨ Thanks @gonzaloriestra! Your snapshot has been published to npm.

Built from 05aabdab8c5e3c742391618db260fd5dcf0fe52a. Workflow run.

Test the snapshot by installing your package globally:

pnpm i -g --@shopify:registry=https://registry.npmjs.org @shopify/cli@0.0.0-snapshot-20261021083201

Caution

After installing, validate the version by running shopify version in your terminal.
If the versions don't match, you might have multiple global instances installed.
Use which shopify to find out which one you are running and uninstall it.

[karreiro]

Thank you for this PR, @gonzaloriestra!

🎩 LGMT!

Before:

After: