fix: anticipate optional chained parameters as undefined when parsing events details#2700
fix: anticipate optional chained parameters as undefined when parsing events details#2700hello-ashleyintech merged 5 commits intomainfrom
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2700 +/- ##
=======================================
Coverage 93.44% 93.44%
=======================================
Files 37 37
Lines 7668 7668
Branches 669 669
=======================================
Hits 7165 7165
Misses 498 498
Partials 5 5 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
🔍 So interesting! I'm noticing the scheduled tests are failing with the following when I run these on my machine: 👁️🗨️ But it's not clear to me which dependencies might've changed to cause this? So curious but will review this in acceptance that dependencies change otherwise. |
zimeg
left a comment
There was a problem hiding this comment.
@hello-ashleyintech LGTM! And thanks for noticing a break in these test!
I'm leaving a few comments of suggestion below but this ought fix tests I believe 🚢 💨
| if (typeof event?.channel === 'string') { | ||
| foundConversationId = event?.channel; | ||
| } else if (typeof event?.channel === 'object' && 'id' in event.channel) { |
There was a problem hiding this comment.
| if (typeof event?.channel === 'string') { | |
| foundConversationId = event?.channel; | |
| } else if (typeof event?.channel === 'object' && 'id' in event.channel) { | |
| if (typeof event.channel === 'string') { | |
| foundConversationId = event?.channel; | |
| } else if (typeof event.channel === 'object' && 'id' in event.channel) { |
🤖 question: We also check that event isn't undefined earlier - are these chainings alright to remove?
Line 39 in 9e1e350
Co-authored-by: Eden Zimbelman <[email protected]>
Co-authored-by: Eden Zimbelman <[email protected]>
Summary
This PR aims to resolve recurring failing tests on
main.Requirements (place an
xin each[ ])