-
Notifications
You must be signed in to change notification settings - Fork 439
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: optional mailbox on warp config #5500
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 2ec2f6b The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
config = await fillDefaults(context, config as any); | ||
|
||
//fillDefaults would have added a mailbox to the config if it was missing | ||
return WarpRouteDeployConfigSchema.parse( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we not use WarpRouteDeployConfigMailboxRequired
to parse then to avoid the type cast?
Description
This PR updates the warp route deployment configuration to handle mailbox addresses more consistently. Key changes:
Drive-by changes
Related issues
#5258
Backward compatibility
Yes - This change maintains backward compatibility while improving the internal handling of mailbox addresses.
Testing
Unit Tests - Existing tests have been updated to accommodate the new mailbox handling approach