Skip to content

Remove dangling buyer-journey #examples link from buyerJourney JSDoc (2026-01)#4523

Merged
majd-shopify merged 2 commits into
2026-01from
rey--remove-buyer-journey-link-2026-01
Jun 23, 2026
Merged

Remove dangling buyer-journey #examples link from buyerJourney JSDoc (2026-01)#4523
majd-shopify merged 2 commits into
2026-01from
rey--remove-buyer-journey-link-2026-01

Conversation

@majd-shopify

Copy link
Copy Markdown
Contributor

Background

A merchant-facing dev docs page was reported broken in this Slack thread: https://shopify.dev/docs/api/checkout-ui-extensions/latest/apis/buyer-journey#examples returns a 404.

The root cause is a self-referential statement in the buyerJourney property's JSDoc in packages/ui-extensions/src/surfaces/checkout/api/standard/standard.ts:

Refer to [buyer journey](/docs/api/checkout-ui-extensions/{API_VERSION}/apis/buyer-journey#examples) examples for more information.

That link is broken two ways: the #examples anchor no longer exists (examples now render via <ExampleSwitcher> at the top of the page), and apis/buyer-journey is the pre-reorg path (docs were reorganized to target-apis/checkout-apis/buyer-journey-api), so it 404s under /latest.

This was already removed at HEAD in World (checkout-web/packages/ui-extensions) in commit 80249b ("Remove self-referential link in buyerJourney prop JSDoc"), but that has not propagated to the published 2026-01 version snapshot, which shopify.dev syncs from this branch.

One of a set of per-version PRs (one per affected release branch: 2025-07, 2025-10, 2026-01, 2026-04, 2026-07-rc).

Solution

Remove the dangling statement from the buyerJourney JSDoc on the 2026-01 branch, mirroring World commit 80249b.

⚠️ Source-only PR. The rendered shopify.dev page won't change until the committed docs/surfaces/checkout/generated/generated_docs_data_v2.json is regenerated via pnpm docs:checkout (docs/surfaces/checkout/build-docs.sh) and committed, then picked up by shopify.dev's once-a-day sync. That regen step is intentionally not included here — flagging for a maintainer to run before/at merge.

Patch authored by River; reported by Kristin Hung.

🎩

  • Docs-comment-only change. Verified the removed text matches World commit 80249b and that git apply --check is clean on this branch.

Checklist

  • I have 🎩'd these changes
  • I have updated relevant documentation

The buyerJourney property's JSDoc pointed at
/docs/api/checkout-ui-extensions/.../apis/buyer-journey#examples, which 404s
under /latest. The docs were reorganized from apis/<name> to
target-apis/checkout-apis/<name>-api, and the #examples anchor no longer
exists (examples now render via the example switcher). This removes the
self-referential statement, mirroring World commit 80249b ("Remove
self-referential link in buyerJourney prop JSDoc").

Source-only change: the committed
docs/surfaces/checkout/generated/generated_docs_data_v2.json artifact still
needs to be regenerated via `pnpm docs:checkout` for the rendered shopify.dev
page to update.

Reported-by: Kristin Hung <kristin.hung@shopify.com>
@github-actions

Copy link
Copy Markdown
Contributor

We detected some changes in packages/*/package.json or packages/*/src, and there are no updates in the .changeset directory. If the changes are user-facing and should cause a version bump, run yarn changeset to track your changes and include them in the next release CHANGELOG. If you are making simple updates to repo configuration, examples, or documentation, you do not need to add a changeset.

@reykjalin reykjalin left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

source changes look good. I didn't look through the newly generated data, but assume it's good.

@mcvinci mcvinci left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🌻

@majd-shopify majd-shopify merged commit 6f856b3 into 2026-01 Jun 23, 2026
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants