-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
fix(aci): fix sending test notification for sentry app #104086
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #104086 +/- ##
===========================================
+ Coverage 79.79% 80.63% +0.83%
===========================================
Files 9317 9319 +2
Lines 397569 397873 +304
Branches 25389 25389
===========================================
+ Hits 317242 320818 +3576
+ Misses 79875 76603 -3272
Partials 452 452 |
| "label": None, | ||
| "value": [ | ||
| {"id": "1dedabd2-059d-457b-ac17-df39031d4593", "type": "team"} | ||
| ], # should stringify this |
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.
Bug: Development comment left in test code
The inline comment # should stringify this at the end of line 399 is a development note that was not meant to be included in the final code. According to the PR discussion, this comment was identified by a reviewer and confirmed by the author that it "should be deleted."
SentryAppFormConfigDataBlobexpectssetting["value"]to be a string. When data comes in from the existing Rule endpoints this may not be the case so we need tojson.dumplists if they come in.We already save json.dumped lists to the
Actiontable.Fixes SENTRY-5BB2