Align CLI fallback routing warnings#111
Conversation
Greptile SummaryThis PR aligns CLI warning logic and documentation with actual server routing behavior: when same-domain function endpoints exist for an inbound domain, fallback endpoints are now suppressed in the warning helper, matching what the server would do. All "catch-all" terminology across CLI templates, OpenAPI specs, and generated SDK code (Node, Go, Python) is replaced with "fallback."
Confidence Score: 5/5Safe to merge — changes are a small, well-tested logic fix in the CLI warning helper and a consistent documentation update across generated SDK files. The routing-suppression logic in No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "Align CLI fallback routing warnings" | Re-trigger Greptile |
Summary
Why
Fallback endpoints only receive managed-domain mail when the inbound domain has no enabled domain-scoped endpoint. The old CLI wording and warning logic could imply multiple functions would receive the same test email when server routing would only deliver to scoped endpoints.
Validation
pnpm --dir cli-node exec vitest run tests/oclif/functions-test-function.test.ts tests/oclif/functions-init.test.tsmake cli-checkCOREPACK_ENABLE_AUTO_PIN=0 make node-checkmake python-checkmake go-checkCOREPACK_ENABLE_AUTO_PIN=0 make shared-checkgit diff --check