-
Notifications
You must be signed in to change notification settings - Fork 313
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 order confirmed event #1601
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
6 Skipped Deployments
|
6ea2e70
to
6545bb1
Compare
}; | ||
|
||
getChannelSlug = () => this.data.order.channel.slug; | ||
getChannelSlug = () => this.rawPayload.order!.channel.slug; |
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.
Question: I'm wondering if we can have private method that either gets this.rawPayload.order
or rejects as having a bunch of !
means we stop checking for nulls - I'm a bit afraid down the road we introduce some change that TypeScript won't catch because of it 🤔
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.
Yea, probably we should somehow fix that. I technically "know" that it's defined - you check this in the factory - but then we assign a type that is too loose.
Will check it again
Scope of the PR
Related issues
Checklist