docs: sync Coming Soon country coverage (add China) - #691

Closed
pengying wants to merge 1 commit into
mainfrom
sync-country-coverage-2026-07
Closed

docs: sync Coming Soon country coverage (add China)#691
pengying wants to merge 1 commit into
mainfrom
sync-country-coverage-2026-07

Conversation

@pengying

@pengyingpengying commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Summary

Syncs mintlify/snippets/country-support.mdx against the Grid Switch Corridor List source of truth.

The only drift is in the Coming Soon table. Applying the filter Public Roadmap (col H) = Yes AND Status (col J) ≠ Live resolves to Canada, China, Hong Kong, South Korea. China (row 87 — Tazapay / Scoping / Public Roadmap = Yes) was missing, so it's added.

Changes

  • Add 🇨🇳 China (CN) to the Coming Soon table, alphabetically after Canada.

Verified already in sync (no change needed)

  • Live table — 62 destinations; the doc's ISO set matches the sheet's Status = Live set exactly.
  • Header FeatureCards and "Send payments to 62 countries" copy — unchanged (Live count is still 62).
  • Regional Summary — Europe 32 / Middle East and Africa 15 / Asia-Pacific 10 / Americas 5 = 62.

Only mintlify/snippets/country-support.mdx is touched, so no OpenAPI rebundle is needed.

Generated by Claude Code

@claude
docs: sync Coming Soon country coverage (add China)
e52a6e5
Sync mintlify/snippets/country-support.mdx against the Grid Switch
Corridor List source of truth. The Coming Soon filter (Public Roadmap =
Yes AND Status != Live) now resolves to Canada, China, Hong Kong, and
South Korea, so add China to the Coming Soon table. The Live table (62
countries) and regional counts already match the sheet — no other
changes needed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G1ymXyjUvzaDPSTS9Rqfrh
@vercel

vercelBot commented Jul 15, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments
ProjectDeploymentActionsUpdated (UTC)
grid-flow-builderIgnoredIgnoredJul 15, 2026 7:11pm
grid-wallet-demoIgnoredIgnoredJul 15, 2026 7:11pm

Request Review

@greptile-apps

greptile-appsBot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR adds 🇨🇳 China (CN) to the "Coming Soon" table in mintlify/snippets/country-support.mdx, syncing against the Grid Switch Corridor List spreadsheet. The change is a single-row insertion placed alphabetically between Canada and Hong Kong.

  • The new row is placed correctly in alphabetical order within the Coming Soon table.
  • China (CN) already exists in the Live table (line 27, Bank Transfer rail), so the page now lists China under both "Live" and "Coming Soon" simultaneously — this may confuse readers unless the two entries represent distinct, clearly-labeled corridors (e.g., a live provider vs. Tazapay still in scoping).

Confidence Score: 4/5

The change is a one-line documentation addition, but it introduces a country that is already listed as Live, leaving readers with contradictory information on the same page.

China (CN) already appears in the Live table with a Bank Transfer rail. Adding it again to the Coming Soon table means the same country is simultaneously advertised as available and as upcoming — readers have no way to reconcile the two entries without out-of-band knowledge of the Tazapay / Scoping context described in the PR.

mintlify/snippets/country-support.mdx — verify whether the duplicate China entry is intentional and, if so, add inline context to distinguish the two corridors.

Important Files Changed

FilenameOverview
mintlify/snippets/country-support.mdxAdds China (CN) to the Coming Soon table; however, China already appears in the Live table, creating a contradictory listing on the same page.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict
Loading
Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---### Issue 1 of 1
mintlify/snippets/country-support.mdx:107
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.

Reviews (1): Last reviewed commit: "docs: sync Coming Soon country coverage ..." | Re-trigger Greptile

greptile-apps[bot]
greptile-appsBot reviewed Jul 15, 2026
View reviewed changes
Comment threadmintlify/snippets/country-support.mdx
| Country | ISO Code |
|---|---|
| 🇨🇦 Canada | CA |
| 🇨🇳 China | CN |

@greptile-appsgreptile-appsBotJul 15, 2026

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.

P1China listed in both Live and Coming Soon tables

🇨🇳 China | CN already appears in the Live table at line 27 (Bank Transfer). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.

Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/country-support.mdx
Line: 107
Comment:
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
How can I resolve this? If you propose a fix, please make it concise.

@jklein24jklein24Jul 30, 2026

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.

@pengying we already have China live, don't we?

@mintlify

mintlifyBot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

ProjectStatusPreviewUpdated (UTC)
Grid🟢 ReadyView PreviewJul 15, 2026, 7:13 PM

@mintlify

mintlifyBot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

ProjectStatusPreviewUpdated (UTC)
Grid🟡 Building–Jul 15, 2026, 7:11 PM

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jklein24jklein24jklein24 left review comments
@greptile-appsgreptile-apps[bot]greptile-apps[bot] left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@pengying@jklein24@claude
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
docs: sync Coming Soon country coverage (add China) - #691
Closed
pengying wants to merge 1 commit into
mainfrom 
sync-country-coverage-2026-07
Closed
docs: sync Coming Soon country coverage (add China)#691
pengying wants to merge 1 commit into
mainfrom 
sync-country-coverage-2026-07
Conversation
@pengying
@pengyingpengying
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Summary
Syncs mintlify/snippets/country-support.mdx against the Grid Switch Corridor List source of truth.
The only drift is in the Coming Soon table. Applying the filter Public Roadmap (col H) = Yes AND Status (col J) ≠ Live resolves to Canada, China, Hong Kong, South Korea. China (row 87 — Tazapay / Scoping / Public Roadmap = Yes) was missing, so it's added.
Changes
  • Add 🇨🇳 China (CN) to the Coming Soon table, alphabetically after Canada.
Verified already in sync (no change needed)
  • Live table — 62 destinations; the doc's ISO set matches the sheet's Status = Live set exactly.
  • Header FeatureCards and "Send payments to 62 countries" copy — unchanged (Live count is still 62).
  • Regional Summary — Europe 32 / Middle East and Africa 15 / Asia-Pacific 10 / Americas 5 = 62.
Only mintlify/snippets/country-support.mdx is touched, so no OpenAPI rebundle is needed.
Generated by Claude Code
@claude
docs: sync Coming Soon country coverage (add China)
e52a6e5
Sync mintlify/snippets/country-support.mdx against the Grid Switch
Corridor List source of truth. The Coming Soon filter (Public Roadmap =
Yes AND Status != Live) now resolves to Canada, China, Hong Kong, and
South Korea, so add China to the Coming Soon table. The Live table (62
countries) and regional counts already match the sheet — no other
changes needed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G1ymXyjUvzaDPSTS9Rqfrh
@vercel
vercelBot
commented
Jul 15, 2026

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
ProjectDeploymentActionsUpdated (UTC)
grid-flow-builderIgnoredIgnoredJul 15, 2026 7:11pm
grid-wallet-demoIgnoredIgnoredJul 15, 2026 7:11pm
Request Review
@greptile-apps
greptile-appsBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Greptile Summary
This PR adds 🇨🇳 China (CN) to the "Coming Soon" table in mintlify/snippets/country-support.mdx, syncing against the Grid Switch Corridor List spreadsheet. The change is a single-row insertion placed alphabetically between Canada and Hong Kong.
  • The new row is placed correctly in alphabetical order within the Coming Soon table.
  • China (CN) already exists in the Live table (line 27, Bank Transfer rail), so the page now lists China under both "Live" and "Coming Soon" simultaneously — this may confuse readers unless the two entries represent distinct, clearly-labeled corridors (e.g., a live provider vs. Tazapay still in scoping).
Confidence Score: 4/5
The change is a one-line documentation addition, but it introduces a country that is already listed as Live, leaving readers with contradictory information on the same page.
China (CN) already appears in the Live table with a Bank Transfer rail. Adding it again to the Coming Soon table means the same country is simultaneously advertised as available and as upcoming — readers have no way to reconcile the two entries without out-of-band knowledge of the Tazapay / Scoping context described in the PR.
mintlify/snippets/country-support.mdx — verify whether the duplicate China entry is intentional and, if so, add inline context to distinguish the two corridors.
Important Files Changed
FilenameOverview
mintlify/snippets/country-support.mdxAdds China (CN) to the Coming Soon table; however, China already appears in the Live table, creating a contradictory listing on the same page.
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict

Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict

Loading
Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---### Issue 1 of 1
mintlify/snippets/country-support.mdx:107
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.

Reviews (1): Last reviewed commit: "docs: sync Coming Soon country coverage ..." | Re-trigger Greptile
greptile-apps[bot]
greptile-appsBot
reviewed
Jul 15, 2026
View reviewed changes
Comment threadmintlify/snippets/country-support.mdx
| Country | ISO Code |
|---|---|
| 🇨🇦 Canada | CA |
| 🇨🇳 China | CN |
@greptile-appsgreptile-appsBotJul 15, 2026

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.

P1China listed in both Live and Coming Soon tables
🇨🇳 China | CN already appears in the Live table at line 27 (Bank Transfer). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/country-support.mdx
Line: 107
Comment:
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
How can I resolve this? If you propose a fix, please make it concise.
@jklein24jklein24Jul 30, 2026

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.

@pengying we already have China live, don't we?
@mintlify
mintlifyBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
ProjectStatusPreviewUpdated (UTC)
Grid🟢 ReadyView PreviewJul 15, 2026, 7:13 PM
@mintlify
mintlifyBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
ProjectStatusPreviewUpdated (UTC)
Grid🟡 Building–Jul 15, 2026, 7:11 PM
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@jklein24jklein24jklein24 left review comments
@greptile-appsgreptile-apps[bot]greptile-apps[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@pengying@jklein24@claude

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
docs: sync Coming Soon country coverage (add China) - #691
Closed
pengying wants to merge 1 commit into
mainfrom 
sync-country-coverage-2026-07
Closed
docs: sync Coming Soon country coverage (add China)#691
pengying wants to merge 1 commit into
mainfrom 
sync-country-coverage-2026-07
Conversation
@pengying
@pengyingpengying
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Summary
Syncs mintlify/snippets/country-support.mdx against the Grid Switch Corridor List source of truth.
The only drift is in the Coming Soon table. Applying the filter Public Roadmap (col H) = Yes AND Status (col J) ≠ Live resolves to Canada, China, Hong Kong, South Korea. China (row 87 — Tazapay / Scoping / Public Roadmap = Yes) was missing, so it's added.
Changes
  • Add 🇨🇳 China (CN) to the Coming Soon table, alphabetically after Canada.
Verified already in sync (no change needed)
  • Live table — 62 destinations; the doc's ISO set matches the sheet's Status = Live set exactly.
  • Header FeatureCards and "Send payments to 62 countries" copy — unchanged (Live count is still 62).
  • Regional Summary — Europe 32 / Middle East and Africa 15 / Asia-Pacific 10 / Americas 5 = 62.
Only mintlify/snippets/country-support.mdx is touched, so no OpenAPI rebundle is needed.
Generated by Claude Code
@claude
docs: sync Coming Soon country coverage (add China)
e52a6e5
Sync mintlify/snippets/country-support.mdx against the Grid Switch
Corridor List source of truth. The Coming Soon filter (Public Roadmap =
Yes AND Status != Live) now resolves to Canada, China, Hong Kong, and
South Korea, so add China to the Coming Soon table. The Live table (62
countries) and regional counts already match the sheet — no other
changes needed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G1ymXyjUvzaDPSTS9Rqfrh
@vercel
vercelBot
commented
Jul 15, 2026

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
ProjectDeploymentActionsUpdated (UTC)
grid-flow-builderIgnoredIgnoredJul 15, 2026 7:11pm
grid-wallet-demoIgnoredIgnoredJul 15, 2026 7:11pm
Request Review
@greptile-apps
greptile-appsBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Greptile Summary
This PR adds 🇨🇳 China (CN) to the "Coming Soon" table in mintlify/snippets/country-support.mdx, syncing against the Grid Switch Corridor List spreadsheet. The change is a single-row insertion placed alphabetically between Canada and Hong Kong.
  • The new row is placed correctly in alphabetical order within the Coming Soon table.
  • China (CN) already exists in the Live table (line 27, Bank Transfer rail), so the page now lists China under both "Live" and "Coming Soon" simultaneously — this may confuse readers unless the two entries represent distinct, clearly-labeled corridors (e.g., a live provider vs. Tazapay still in scoping).
Confidence Score: 4/5
The change is a one-line documentation addition, but it introduces a country that is already listed as Live, leaving readers with contradictory information on the same page.
China (CN) already appears in the Live table with a Bank Transfer rail. Adding it again to the Coming Soon table means the same country is simultaneously advertised as available and as upcoming — readers have no way to reconcile the two entries without out-of-band knowledge of the Tazapay / Scoping context described in the PR.
mintlify/snippets/country-support.mdx — verify whether the duplicate China entry is intentional and, if so, add inline context to distinguish the two corridors.
Important Files Changed
FilenameOverview
mintlify/snippets/country-support.mdxAdds China (CN) to the Coming Soon table; however, China already appears in the Live table, creating a contradictory listing on the same page.
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict

Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict

Loading
Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---### Issue 1 of 1
mintlify/snippets/country-support.mdx:107
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.

Reviews (1): Last reviewed commit: "docs: sync Coming Soon country coverage ..." | Re-trigger Greptile
greptile-apps[bot]
greptile-appsBot
reviewed
Jul 15, 2026
View reviewed changes
Comment threadmintlify/snippets/country-support.mdx
| Country | ISO Code |
|---|---|
| 🇨🇦 Canada | CA |
| 🇨🇳 China | CN |
@greptile-appsgreptile-appsBotJul 15, 2026

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.

P1China listed in both Live and Coming Soon tables
🇨🇳 China | CN already appears in the Live table at line 27 (Bank Transfer). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/country-support.mdx
Line: 107
Comment:
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
How can I resolve this? If you propose a fix, please make it concise.
@jklein24jklein24Jul 30, 2026

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.

@pengying we already have China live, don't we?
@mintlify
mintlifyBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
ProjectStatusPreviewUpdated (UTC)
Grid🟢 ReadyView PreviewJul 15, 2026, 7:13 PM
@mintlify
mintlifyBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
ProjectStatusPreviewUpdated (UTC)
Grid🟡 Building–Jul 15, 2026, 7:11 PM
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@jklein24jklein24jklein24 left review comments
@greptile-appsgreptile-apps[bot]greptile-apps[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@pengying@jklein24@claude

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
docs: sync Coming Soon country coverage (add China) - #691
Closed
pengying wants to merge 1 commit into
mainfrom 
sync-country-coverage-2026-07
Closed
docs: sync Coming Soon country coverage (add China)#691
pengying wants to merge 1 commit into
mainfrom 
sync-country-coverage-2026-07
Conversation
@pengying
@pengyingpengying
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Summary
Syncs mintlify/snippets/country-support.mdx against the Grid Switch Corridor List source of truth.
The only drift is in the Coming Soon table. Applying the filter Public Roadmap (col H) = Yes AND Status (col J) ≠ Live resolves to Canada, China, Hong Kong, South Korea. China (row 87 — Tazapay / Scoping / Public Roadmap = Yes) was missing, so it's added.
Changes
  • Add 🇨🇳 China (CN) to the Coming Soon table, alphabetically after Canada.
Verified already in sync (no change needed)
  • Live table — 62 destinations; the doc's ISO set matches the sheet's Status = Live set exactly.
  • Header FeatureCards and "Send payments to 62 countries" copy — unchanged (Live count is still 62).
  • Regional Summary — Europe 32 / Middle East and Africa 15 / Asia-Pacific 10 / Americas 5 = 62.
Only mintlify/snippets/country-support.mdx is touched, so no OpenAPI rebundle is needed.
Generated by Claude Code
@claude
docs: sync Coming Soon country coverage (add China)
e52a6e5
Sync mintlify/snippets/country-support.mdx against the Grid Switch
Corridor List source of truth. The Coming Soon filter (Public Roadmap =
Yes AND Status != Live) now resolves to Canada, China, Hong Kong, and
South Korea, so add China to the Coming Soon table. The Live table (62
countries) and regional counts already match the sheet — no other
changes needed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G1ymXyjUvzaDPSTS9Rqfrh
@vercel
vercelBot
commented
Jul 15, 2026

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
ProjectDeploymentActionsUpdated (UTC)
grid-flow-builderIgnoredIgnoredJul 15, 2026 7:11pm
grid-wallet-demoIgnoredIgnoredJul 15, 2026 7:11pm
Request Review
@greptile-apps
greptile-appsBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Greptile Summary
This PR adds 🇨🇳 China (CN) to the "Coming Soon" table in mintlify/snippets/country-support.mdx, syncing against the Grid Switch Corridor List spreadsheet. The change is a single-row insertion placed alphabetically between Canada and Hong Kong.
  • The new row is placed correctly in alphabetical order within the Coming Soon table.
  • China (CN) already exists in the Live table (line 27, Bank Transfer rail), so the page now lists China under both "Live" and "Coming Soon" simultaneously — this may confuse readers unless the two entries represent distinct, clearly-labeled corridors (e.g., a live provider vs. Tazapay still in scoping).
Confidence Score: 4/5
The change is a one-line documentation addition, but it introduces a country that is already listed as Live, leaving readers with contradictory information on the same page.
China (CN) already appears in the Live table with a Bank Transfer rail. Adding it again to the Coming Soon table means the same country is simultaneously advertised as available and as upcoming — readers have no way to reconcile the two entries without out-of-band knowledge of the Tazapay / Scoping context described in the PR.
mintlify/snippets/country-support.mdx — verify whether the duplicate China entry is intentional and, if so, add inline context to distinguish the two corridors.
Important Files Changed
FilenameOverview
mintlify/snippets/country-support.mdxAdds China (CN) to the Coming Soon table; however, China already appears in the Live table, creating a contradictory listing on the same page.
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict

Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict

Loading
Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---### Issue 1 of 1
mintlify/snippets/country-support.mdx:107
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.

Reviews (1): Last reviewed commit: "docs: sync Coming Soon country coverage ..." | Re-trigger Greptile
greptile-apps[bot]
greptile-appsBot
reviewed
Jul 15, 2026
View reviewed changes
Comment threadmintlify/snippets/country-support.mdx
| Country | ISO Code |
|---|---|
| 🇨🇦 Canada | CA |
| 🇨🇳 China | CN |
@greptile-appsgreptile-appsBotJul 15, 2026

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.

P1China listed in both Live and Coming Soon tables
🇨🇳 China | CN already appears in the Live table at line 27 (Bank Transfer). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/country-support.mdx
Line: 107
Comment:
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
How can I resolve this? If you propose a fix, please make it concise.
@jklein24jklein24Jul 30, 2026

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.

@pengying we already have China live, don't we?
@mintlify
mintlifyBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
ProjectStatusPreviewUpdated (UTC)
Grid🟢 ReadyView PreviewJul 15, 2026, 7:13 PM
@mintlify
mintlifyBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
ProjectStatusPreviewUpdated (UTC)
Grid🟡 Building–Jul 15, 2026, 7:11 PM
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@jklein24jklein24jklein24 left review comments
@greptile-appsgreptile-apps[bot]greptile-apps[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@pengying@jklein24@claude

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
docs: sync Coming Soon country coverage (add China) - #691
Closed
pengying wants to merge 1 commit into
mainfrom 
sync-country-coverage-2026-07
Closed
docs: sync Coming Soon country coverage (add China)#691
pengying wants to merge 1 commit into
mainfrom 
sync-country-coverage-2026-07
Conversation
@pengying
@pengyingpengying
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Summary
Syncs mintlify/snippets/country-support.mdx against the Grid Switch Corridor List source of truth.
The only drift is in the Coming Soon table. Applying the filter Public Roadmap (col H) = Yes AND Status (col J) ≠ Live resolves to Canada, China, Hong Kong, South Korea. China (row 87 — Tazapay / Scoping / Public Roadmap = Yes) was missing, so it's added.
Changes
  • Add 🇨🇳 China (CN) to the Coming Soon table, alphabetically after Canada.
Verified already in sync (no change needed)
  • Live table — 62 destinations; the doc's ISO set matches the sheet's Status = Live set exactly.
  • Header FeatureCards and "Send payments to 62 countries" copy — unchanged (Live count is still 62).
  • Regional Summary — Europe 32 / Middle East and Africa 15 / Asia-Pacific 10 / Americas 5 = 62.
Only mintlify/snippets/country-support.mdx is touched, so no OpenAPI rebundle is needed.
Generated by Claude Code
@claude
docs: sync Coming Soon country coverage (add China)
e52a6e5
Sync mintlify/snippets/country-support.mdx against the Grid Switch
Corridor List source of truth. The Coming Soon filter (Public Roadmap =
Yes AND Status != Live) now resolves to Canada, China, Hong Kong, and
South Korea, so add China to the Coming Soon table. The Live table (62
countries) and regional counts already match the sheet — no other
changes needed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G1ymXyjUvzaDPSTS9Rqfrh
@vercel
vercelBot
commented
Jul 15, 2026

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
ProjectDeploymentActionsUpdated (UTC)
grid-flow-builderIgnoredIgnoredJul 15, 2026 7:11pm
grid-wallet-demoIgnoredIgnoredJul 15, 2026 7:11pm
Request Review
@greptile-apps
greptile-appsBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Greptile Summary
This PR adds 🇨🇳 China (CN) to the "Coming Soon" table in mintlify/snippets/country-support.mdx, syncing against the Grid Switch Corridor List spreadsheet. The change is a single-row insertion placed alphabetically between Canada and Hong Kong.
  • The new row is placed correctly in alphabetical order within the Coming Soon table.
  • China (CN) already exists in the Live table (line 27, Bank Transfer rail), so the page now lists China under both "Live" and "Coming Soon" simultaneously — this may confuse readers unless the two entries represent distinct, clearly-labeled corridors (e.g., a live provider vs. Tazapay still in scoping).
Confidence Score: 4/5
The change is a one-line documentation addition, but it introduces a country that is already listed as Live, leaving readers with contradictory information on the same page.
China (CN) already appears in the Live table with a Bank Transfer rail. Adding it again to the Coming Soon table means the same country is simultaneously advertised as available and as upcoming — readers have no way to reconcile the two entries without out-of-band knowledge of the Tazapay / Scoping context described in the PR.
mintlify/snippets/country-support.mdx — verify whether the duplicate China entry is intentional and, if so, add inline context to distinguish the two corridors.
Important Files Changed
FilenameOverview
mintlify/snippets/country-support.mdxAdds China (CN) to the Coming Soon table; however, China already appears in the Live table, creating a contradictory listing on the same page.
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict

Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict

Loading
Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---### Issue 1 of 1
mintlify/snippets/country-support.mdx:107
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.

Reviews (1): Last reviewed commit: "docs: sync Coming Soon country coverage ..." | Re-trigger Greptile
greptile-apps[bot]
greptile-appsBot
reviewed
Jul 15, 2026
View reviewed changes
Comment threadmintlify/snippets/country-support.mdx
| Country | ISO Code |
|---|---|
| 🇨🇦 Canada | CA |
| 🇨🇳 China | CN |
@greptile-appsgreptile-appsBotJul 15, 2026

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.

P1China listed in both Live and Coming Soon tables
🇨🇳 China | CN already appears in the Live table at line 27 (Bank Transfer). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/country-support.mdx
Line: 107
Comment:
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
How can I resolve this? If you propose a fix, please make it concise.
@jklein24jklein24Jul 30, 2026

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.

@pengying we already have China live, don't we?
@mintlify
mintlifyBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
ProjectStatusPreviewUpdated (UTC)
Grid🟢 ReadyView PreviewJul 15, 2026, 7:13 PM
@mintlify
mintlifyBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
ProjectStatusPreviewUpdated (UTC)
Grid🟡 Building–Jul 15, 2026, 7:11 PM
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@jklein24jklein24jklein24 left review comments
@greptile-appsgreptile-apps[bot]greptile-apps[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@pengying@jklein24@claude

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
docs: sync Coming Soon country coverage (add China) - #691
Closed
pengying wants to merge 1 commit into
mainfrom 
sync-country-coverage-2026-07
Closed
docs: sync Coming Soon country coverage (add China)#691
pengying wants to merge 1 commit into
mainfrom 
sync-country-coverage-2026-07
Conversation
@pengying
@pengyingpengying
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Summary
Syncs mintlify/snippets/country-support.mdx against the Grid Switch Corridor List source of truth.
The only drift is in the Coming Soon table. Applying the filter Public Roadmap (col H) = Yes AND Status (col J) ≠ Live resolves to Canada, China, Hong Kong, South Korea. China (row 87 — Tazapay / Scoping / Public Roadmap = Yes) was missing, so it's added.
Changes
  • Add 🇨🇳 China (CN) to the Coming Soon table, alphabetically after Canada.
Verified already in sync (no change needed)
  • Live table — 62 destinations; the doc's ISO set matches the sheet's Status = Live set exactly.
  • Header FeatureCards and "Send payments to 62 countries" copy — unchanged (Live count is still 62).
  • Regional Summary — Europe 32 / Middle East and Africa 15 / Asia-Pacific 10 / Americas 5 = 62.
Only mintlify/snippets/country-support.mdx is touched, so no OpenAPI rebundle is needed.
Generated by Claude Code
@claude
docs: sync Coming Soon country coverage (add China)
e52a6e5
Sync mintlify/snippets/country-support.mdx against the Grid Switch
Corridor List source of truth. The Coming Soon filter (Public Roadmap =
Yes AND Status != Live) now resolves to Canada, China, Hong Kong, and
South Korea, so add China to the Coming Soon table. The Live table (62
countries) and regional counts already match the sheet — no other
changes needed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G1ymXyjUvzaDPSTS9Rqfrh
@vercel
vercelBot
commented
Jul 15, 2026

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
ProjectDeploymentActionsUpdated (UTC)
grid-flow-builderIgnoredIgnoredJul 15, 2026 7:11pm
grid-wallet-demoIgnoredIgnoredJul 15, 2026 7:11pm
Request Review
@greptile-apps
greptile-appsBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Greptile Summary
This PR adds 🇨🇳 China (CN) to the "Coming Soon" table in mintlify/snippets/country-support.mdx, syncing against the Grid Switch Corridor List spreadsheet. The change is a single-row insertion placed alphabetically between Canada and Hong Kong.
  • The new row is placed correctly in alphabetical order within the Coming Soon table.
  • China (CN) already exists in the Live table (line 27, Bank Transfer rail), so the page now lists China under both "Live" and "Coming Soon" simultaneously — this may confuse readers unless the two entries represent distinct, clearly-labeled corridors (e.g., a live provider vs. Tazapay still in scoping).
Confidence Score: 4/5
The change is a one-line documentation addition, but it introduces a country that is already listed as Live, leaving readers with contradictory information on the same page.
China (CN) already appears in the Live table with a Bank Transfer rail. Adding it again to the Coming Soon table means the same country is simultaneously advertised as available and as upcoming — readers have no way to reconcile the two entries without out-of-band knowledge of the Tazapay / Scoping context described in the PR.
mintlify/snippets/country-support.mdx — verify whether the duplicate China entry is intentional and, if so, add inline context to distinguish the two corridors.
Important Files Changed
FilenameOverview
mintlify/snippets/country-support.mdxAdds China (CN) to the Coming Soon table; however, China already appears in the Live table, creating a contradictory listing on the same page.
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict

Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict

Loading
Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---### Issue 1 of 1
mintlify/snippets/country-support.mdx:107
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.

Reviews (1): Last reviewed commit: "docs: sync Coming Soon country coverage ..." | Re-trigger Greptile
greptile-apps[bot]
greptile-appsBot
reviewed
Jul 15, 2026
View reviewed changes
Comment threadmintlify/snippets/country-support.mdx
| Country | ISO Code |
|---|---|
| 🇨🇦 Canada | CA |
| 🇨🇳 China | CN |
@greptile-appsgreptile-appsBotJul 15, 2026

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.

P1China listed in both Live and Coming Soon tables
🇨🇳 China | CN already appears in the Live table at line 27 (Bank Transfer). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/country-support.mdx
Line: 107
Comment:
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
How can I resolve this? If you propose a fix, please make it concise.
@jklein24jklein24Jul 30, 2026

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.

@pengying we already have China live, don't we?
@mintlify
mintlifyBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
ProjectStatusPreviewUpdated (UTC)
Grid🟢 ReadyView PreviewJul 15, 2026, 7:13 PM
@mintlify
mintlifyBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
ProjectStatusPreviewUpdated (UTC)
Grid🟡 Building–Jul 15, 2026, 7:11 PM
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@jklein24jklein24jklein24 left review comments
@greptile-appsgreptile-apps[bot]greptile-apps[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@pengying@jklein24@claude

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
docs: sync Coming Soon country coverage (add China) - #691
Closed
pengying wants to merge 1 commit into
mainfrom 
sync-country-coverage-2026-07
Closed
docs: sync Coming Soon country coverage (add China)#691
pengying wants to merge 1 commit into
mainfrom 
sync-country-coverage-2026-07
Conversation
@pengying
@pengyingpengying
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Summary
Syncs mintlify/snippets/country-support.mdx against the Grid Switch Corridor List source of truth.
The only drift is in the Coming Soon table. Applying the filter Public Roadmap (col H) = Yes AND Status (col J) ≠ Live resolves to Canada, China, Hong Kong, South Korea. China (row 87 — Tazapay / Scoping / Public Roadmap = Yes) was missing, so it's added.
Changes
  • Add 🇨🇳 China (CN) to the Coming Soon table, alphabetically after Canada.
Verified already in sync (no change needed)
  • Live table — 62 destinations; the doc's ISO set matches the sheet's Status = Live set exactly.
  • Header FeatureCards and "Send payments to 62 countries" copy — unchanged (Live count is still 62).
  • Regional Summary — Europe 32 / Middle East and Africa 15 / Asia-Pacific 10 / Americas 5 = 62.
Only mintlify/snippets/country-support.mdx is touched, so no OpenAPI rebundle is needed.
Generated by Claude Code
@claude
docs: sync Coming Soon country coverage (add China)
e52a6e5
Sync mintlify/snippets/country-support.mdx against the Grid Switch
Corridor List source of truth. The Coming Soon filter (Public Roadmap =
Yes AND Status != Live) now resolves to Canada, China, Hong Kong, and
South Korea, so add China to the Coming Soon table. The Live table (62
countries) and regional counts already match the sheet — no other
changes needed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G1ymXyjUvzaDPSTS9Rqfrh
@vercel
vercelBot
commented
Jul 15, 2026

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
ProjectDeploymentActionsUpdated (UTC)
grid-flow-builderIgnoredIgnoredJul 15, 2026 7:11pm
grid-wallet-demoIgnoredIgnoredJul 15, 2026 7:11pm
Request Review
@greptile-apps
greptile-appsBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Greptile Summary
This PR adds 🇨🇳 China (CN) to the "Coming Soon" table in mintlify/snippets/country-support.mdx, syncing against the Grid Switch Corridor List spreadsheet. The change is a single-row insertion placed alphabetically between Canada and Hong Kong.
  • The new row is placed correctly in alphabetical order within the Coming Soon table.
  • China (CN) already exists in the Live table (line 27, Bank Transfer rail), so the page now lists China under both "Live" and "Coming Soon" simultaneously — this may confuse readers unless the two entries represent distinct, clearly-labeled corridors (e.g., a live provider vs. Tazapay still in scoping).
Confidence Score: 4/5
The change is a one-line documentation addition, but it introduces a country that is already listed as Live, leaving readers with contradictory information on the same page.
China (CN) already appears in the Live table with a Bank Transfer rail. Adding it again to the Coming Soon table means the same country is simultaneously advertised as available and as upcoming — readers have no way to reconcile the two entries without out-of-band knowledge of the Tazapay / Scoping context described in the PR.
mintlify/snippets/country-support.mdx — verify whether the duplicate China entry is intentional and, if so, add inline context to distinguish the two corridors.
Important Files Changed
FilenameOverview
mintlify/snippets/country-support.mdxAdds China (CN) to the Coming Soon table; however, China already appears in the Live table, creating a contradictory listing on the same page.
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict

Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict

Loading
Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---### Issue 1 of 1
mintlify/snippets/country-support.mdx:107
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.

Reviews (1): Last reviewed commit: "docs: sync Coming Soon country coverage ..." | Re-trigger Greptile
greptile-apps[bot]
greptile-appsBot
reviewed
Jul 15, 2026
View reviewed changes
Comment threadmintlify/snippets/country-support.mdx
| Country | ISO Code |
|---|---|
| 🇨🇦 Canada | CA |
| 🇨🇳 China | CN |
@greptile-appsgreptile-appsBotJul 15, 2026

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.

P1China listed in both Live and Coming Soon tables
🇨🇳 China | CN already appears in the Live table at line 27 (Bank Transfer). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/country-support.mdx
Line: 107
Comment:
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
How can I resolve this? If you propose a fix, please make it concise.
@jklein24jklein24Jul 30, 2026

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.

@pengying we already have China live, don't we?
@mintlify
mintlifyBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
ProjectStatusPreviewUpdated (UTC)
Grid🟢 ReadyView PreviewJul 15, 2026, 7:13 PM
@mintlify
mintlifyBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
ProjectStatusPreviewUpdated (UTC)
Grid🟡 Building–Jul 15, 2026, 7:11 PM
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@jklein24jklein24jklein24 left review comments
@greptile-appsgreptile-apps[bot]greptile-apps[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@pengying@jklein24@claude

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
docs: sync Coming Soon country coverage (add China) - #691
Closed
pengying wants to merge 1 commit into
mainfrom 
sync-country-coverage-2026-07
Closed
docs: sync Coming Soon country coverage (add China)#691
pengying wants to merge 1 commit into
mainfrom 
sync-country-coverage-2026-07
Conversation
@pengying
@pengyingpengying
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Summary
Syncs mintlify/snippets/country-support.mdx against the Grid Switch Corridor List source of truth.
The only drift is in the Coming Soon table. Applying the filter Public Roadmap (col H) = Yes AND Status (col J) ≠ Live resolves to Canada, China, Hong Kong, South Korea. China (row 87 — Tazapay / Scoping / Public Roadmap = Yes) was missing, so it's added.
Changes
  • Add 🇨🇳 China (CN) to the Coming Soon table, alphabetically after Canada.
Verified already in sync (no change needed)
  • Live table — 62 destinations; the doc's ISO set matches the sheet's Status = Live set exactly.
  • Header FeatureCards and "Send payments to 62 countries" copy — unchanged (Live count is still 62).
  • Regional Summary — Europe 32 / Middle East and Africa 15 / Asia-Pacific 10 / Americas 5 = 62.
Only mintlify/snippets/country-support.mdx is touched, so no OpenAPI rebundle is needed.
Generated by Claude Code
@claude
docs: sync Coming Soon country coverage (add China)
e52a6e5
Sync mintlify/snippets/country-support.mdx against the Grid Switch
Corridor List source of truth. The Coming Soon filter (Public Roadmap =
Yes AND Status != Live) now resolves to Canada, China, Hong Kong, and
South Korea, so add China to the Coming Soon table. The Live table (62
countries) and regional counts already match the sheet — no other
changes needed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01G1ymXyjUvzaDPSTS9Rqfrh
@vercel
vercelBot
commented
Jul 15, 2026

Copy link


Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
ProjectDeploymentActionsUpdated (UTC)
grid-flow-builderIgnoredIgnoredJul 15, 2026 7:11pm
grid-wallet-demoIgnoredIgnoredJul 15, 2026 7:11pm
Request Review
@greptile-apps
greptile-appsBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Greptile Summary
This PR adds 🇨🇳 China (CN) to the "Coming Soon" table in mintlify/snippets/country-support.mdx, syncing against the Grid Switch Corridor List spreadsheet. The change is a single-row insertion placed alphabetically between Canada and Hong Kong.
  • The new row is placed correctly in alphabetical order within the Coming Soon table.
  • China (CN) already exists in the Live table (line 27, Bank Transfer rail), so the page now lists China under both "Live" and "Coming Soon" simultaneously — this may confuse readers unless the two entries represent distinct, clearly-labeled corridors (e.g., a live provider vs. Tazapay still in scoping).
Confidence Score: 4/5
The change is a one-line documentation addition, but it introduces a country that is already listed as Live, leaving readers with contradictory information on the same page.
China (CN) already appears in the Live table with a Bank Transfer rail. Adding it again to the Coming Soon table means the same country is simultaneously advertised as available and as upcoming — readers have no way to reconcile the two entries without out-of-band knowledge of the Tazapay / Scoping context described in the PR.
mintlify/snippets/country-support.mdx — verify whether the duplicate China entry is intentional and, if so, add inline context to distinguish the two corridors.
Important Files Changed
FilenameOverview
mintlify/snippets/country-support.mdxAdds China (CN) to the Coming Soon table; however, China already appears in the Live table, creating a contradictory listing on the same page.
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict

Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
Sheet["Grid Switch Corridor List\n(Source of Truth)"] --> Filter["Filter: Public Roadmap = Yes\nAND Status ≠ Live"]
Filter --> ComingSoon["Coming Soon Countries\nCA, CN, HK, KR"]
ComingSoon --> Doc["country-support.mdx\nComing Soon Table"]
Sheet --> LiveFilter["Filter: Status = Live\n(62 countries)"]
LiveFilter --> LiveTable["country-support.mdx\nLive Table"]
LiveTable -- "CN already here (line 27)" --> Conflict["⚠️ China appears\nin BOTH tables"]
Doc -- "CN added by this PR" --> Conflict

Loading
Prompt To Fix All With AI
Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---### Issue 1 of 1
mintlify/snippets/country-support.mdx:107
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.

Reviews (1): Last reviewed commit: "docs: sync Coming Soon country coverage ..." | Re-trigger Greptile
greptile-apps[bot]
greptile-appsBot
reviewed
Jul 15, 2026
View reviewed changes
Comment threadmintlify/snippets/country-support.mdx
| Country | ISO Code |
|---|---|
| 🇨🇦 Canada | CA |
| 🇨🇳 China | CN |
@greptile-appsgreptile-appsBotJul 15, 2026

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.

P1China listed in both Live and Coming Soon tables
🇨🇳 China | CN already appears in the Live table at line 27 (Bank Transfer). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/country-support.mdx
Line: 107
Comment:
**China listed in both Live and Coming Soon tables**`🇨🇳 China | CN` already appears in the Live table at line 27 (`Bank Transfer`). Adding it a second time to the Coming Soon table means readers will see China classified as both an active destination and an upcoming one on the same page, which is contradictory. If the intent is to surface a second, distinct corridor for China (e.g., Tazapay / Scoping alongside an already-live Bank Transfer route), the doc should clarify that distinction; otherwise one of the entries should be removed.
How can I resolve this? If you propose a fix, please make it concise.
@jklein24jklein24Jul 30, 2026

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.

@pengying we already have China live, don't we?
@mintlify
mintlifyBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
ProjectStatusPreviewUpdated (UTC)
Grid🟢 ReadyView PreviewJul 15, 2026, 7:13 PM
@mintlify
mintlifyBot
commented
Jul 15, 2026

Copy link


Copy Markdown

Contributor
Preview deployment for your docs. Learn more about Mintlify Previews.
ProjectStatusPreviewUpdated (UTC)
Grid🟡 Building–Jul 15, 2026, 7:11 PM
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers

@jklein24jklein24jklein24 left review comments
@greptile-appsgreptile-apps[bot]greptile-apps[bot] left review comments

Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

3 participants

@pengying@jklein24@claude