-
Notifications
You must be signed in to change notification settings - Fork 12
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: remove pubsub "fail_XX_YY" messages #1013
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1013 +/- ##
==========================================
- Coverage 94.94% 94.91% -0.03%
==========================================
Files 185 185
Lines 5339 5272 -67
Branches 509 508 -1
==========================================
- Hits 5069 5004 -65
+ Misses 235 233 -2
Partials 35 35
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Sourcery Code Quality Report✅ Merging this PR will increase code quality in the affected files by 0.42%.
Here are some functions in these files that still need a tune-up:
Legend and ExplanationThe emojis denote the absolute quality of the code:
The 👍 and 👎 indicate whether the quality has improved or gotten worse with this pull request. Please see our documentation here for details on how these metrics are calculated. We are actively working on this report - lots more documentation and extra metrics to come! Help us improve this quality report! |
Kudos, SonarCloud Quality Gate passed!
|
Does this PR introduce a breaking change?
Describe the purpose of this pull request.
To deal with the "fail_XX_YY" messages being sent. The original issue wanted to clean up the naming of the payload, but investigation found these messages were redundant and should just be removed.
Describe how this was implemented.
Removed all the "fail_XX_YY" messages. Where XX was insert, delete, select, etc. Replaced with "do_log_debug" messages.
Messages such as "fail_calculate_YY" remain and need to be handled by a message dialog for the user. The message dialog should also handle the "do_log_debug" messages since the user should be notified when one of these events occurs, but it doesn't necessarily need to be logged.
Describe any particular area(s) reviewers should focus on.
None
Provide any other pertinent information.
Closes #333
Pull Request Checklist
Code Style
Static Checks
this PR.
Tests
Chores
this PR. These problem areas have been decorated with an ISSUE: # comment.