From 02e8d2b0aba04fe507f15c7ffe137ba722d13584 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 12 Mar 2026 03:43:19 +0000 Subject: [PATCH 1/2] Initial plan From e14faf0b4445066eaa974716fb6bb2349bec764a Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 12 Mar 2026 03:50:48 +0000 Subject: [PATCH 2/2] Remove stale comments about SpecParser defaulting to RUNTIME_REQUIRED_TABLES Co-authored-by: kdhillon-stripe <243457111+kdhillon-stripe@users.noreply.github.com> --- packages/sync-engine/scripts/test-table-modes.ts | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/packages/sync-engine/scripts/test-table-modes.ts b/packages/sync-engine/scripts/test-table-modes.ts index 10cb3b97..99b5ac28 100644 --- a/packages/sync-engine/scripts/test-table-modes.ts +++ b/packages/sync-engine/scripts/test-table-modes.ts @@ -38,11 +38,10 @@ async function main() { console.log(`Table names: ${runtimeRequiredSpec.tables.map((t) => t.tableName).join(', ')}`) console.log() - // Test all_projected mode (omit allowedTables per the interface documentation) + // Test all_projected mode (omit allowedTables to parse all resolvable x-resourceId entries) const allProjectedSpec = parser.parse(resolvedSpec.spec, { resourceAliases: OPENAPI_RESOURCE_TABLE_ALIASES, - // No allowedTables property - per types.ts: "If omitted, all resolvable x-resourceId entries are parsed" - // Note: Current implementation defaults to RUNTIME_REQUIRED_TABLES when omitted + // No allowedTables property - all resolvable x-resourceId entries are parsed }) console.log('=== all_projected mode ===') @@ -67,12 +66,6 @@ async function main() { additionalTables.forEach((name) => console.log(` - ${name}`)) } else { console.log('No additional tables found in all_projected mode.') - console.log( - 'Note: The SpecParser defaults to RUNTIME_REQUIRED_TABLES when allowedTables is omitted.' - ) - console.log( - 'This means the parser scope may be the actual bottleneck, not the migration filtering.' - ) } }