Repository navigation
Preserve universal Gateway links through organization creation - #1096
softmarshmallow wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
6 Skipped Deployments
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe console destination validator now accepts the exact ChangesUniversal Gateway alias
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Feature Merge Risk: ⚪ Minimal · up to This adds an opt-in return path for the Gateway link after organization creation. Other redirect targets are still rejected, and no actionable merge risk was found. Pre-merge checks |
|
31a47ba to
fa86f26
Compare
Allow the exact
https://console.grida.co/_/ai-gatewaycontinuation through Grida's existing organization-creation handoff, so callers can return users to the same Gateway entry point after creation.This is optional continuation support. The current Console organization-creation button returns to
/, so this change alone does not alter that flow. Callers must explicitly supplyreturn_to=/_/ai-gatewayto use it. The billing alias is outside this PR.Adds the alias to the finite destination validator and contract fixtures, with a handler test covering successful organization creation and anonymous sign-in continuation. Organization authority and creation behavior remain unchanged; arbitrary redirect URLs and nested/query-bearing aliases remain rejected.
Existing destination and account-handoff fixtures now use explicit test IDs
1and2, with0retained as an invalid case. Fixtures document that example IDs are synthetic constants.Validation: 154 focused Console-management/account tests passed locally, including the existing rejection cases. Formatting and lint passed. The original candidate also passed editor TypeScript checks. No database migration or payment changes.