Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Overview
This PR will address the following Issue/Feature: [#137]
This PR will result in the following new package version: 0.14.1
No fields are changed, just the logic of how some fields are calculated.
Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:
Bug Fixes
nullif
logic to account for "divide by zero" errors inint_quickbooks__deposit_double_entry
andint_quickbooks__deposit_transactions
for whentotal_amount
values from thedeposit
source tableare zero.
Under the Hood
int_quickbooks__deposit_double_entry
and deposittransaction_type
values inquickbooks__general_ledger
.integration_tests
to reproduce issue and confirm fixes.PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
Before marking this PR as "ready for review" the following have been applied:
Detailed Validation
Please share any and all of your validation steps:
After modifying the seed files, we were able to reproduce the error. customers were experiencing.
Adding the
nullif
logic resolved the errors.We also constructed an additional integrity test
deposit_ledger_amounts_match
to ensure that there are no discrepancies on amounts from the new logic.If you had to summarize this PR in an emoji, which would it be?
0️⃣