-
Notifications
You must be signed in to change notification settings - Fork 1.5k
remove unused globalSettings parameter from send responses
#6016
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
remove unused globalSettings parameter from send responses
#6016
Conversation
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6016 +/- ##
==========================================
+ Coverage 47.83% 47.84% +0.01%
==========================================
Files 1700 1702 +2
Lines 75484 75532 +48
Branches 6794 6799 +5
==========================================
+ Hits 36107 36142 +35
- Misses 37911 37923 +12
- Partials 1466 1467 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
New Issues (5)Checkmarx found the following issues in this Pull Request
Fixed Issues (14)Great job! The following issues were fixed in this Pull Request
|
|
djsmith85
left a comment
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.
This should only be removing the usage of unused globalSettings. The last commit (5f84072) introduces the new ISendOwnerQuery which was created for #5895. I think this might have been a bad merge/push.
You could either update this PR and we'll get it merged quickly, or close this and include the clean up on #5895
Pull request was closed







🎟️ Tracking
#5895 - code review feedback
📔 Objective
Remove unused
globalSettingsparameter from send responses⏰ Reminders before review
🦮 Reviewer guidelines
:+1:) or similar for great changes:memo:) or ℹ️ (:information_source:) for notes or general info:question:) for questions:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:) for suggestions / improvements:x:) or:warning:) for more significant problems or concerns needing attention:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt:pick:) for minor or nitpick changes