-
Notifications
You must be signed in to change notification settings - Fork 6.2k
JSON escape complex strings in Slack attachments JSON (#8665) #11098
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
base: master
Are you sure you want to change the base?
JSON escape complex strings in Slack attachments JSON (#8665) #11098
Conversation
3d52c2d
to
b91fcbd
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #11098 +/- ##
==========================================
+ Coverage 60.23% 60.25% +0.01%
==========================================
Files 346 346
Lines 59212 59212
==========================================
+ Hits 35668 35678 +10
+ Misses 20664 20658 -6
+ Partials 2880 2876 -4 ☔ View full report in Codecov by Sentry. |
Signed-off-by: paul alvarez <[email protected]>
Signed-off-by: paul alvarez <[email protected]>
ab79b5e
to
de58cfd
Compare
+1 for documenting this
For example, it generates invalid JSON if the string contains There are probably other scenarios where |
Confirming that |
Closed the PR due to it being old and unlikely to be able to resolve merge conflicts. But feel free to re-open/re-submit if the work is still planned. |
Is only the rebase needed? |
❌ Preview Environment undeployed from BunnyshellAvailable commands (reply to this comment):
|
Maybe only rebase, but it's been a while, maybe more is needed |
Note on DCO:
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.
Checklist:
Fixes #8665