-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2024-02-26] [HIGH] Move the policy tax enabled property to tax key #36176
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01c25bc5a392761ffc |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @ishpaul777 ( |
@mountiny, @ishpaul777 Whoops! This issue is 2 days overdue. Let's get this updated quick! |
I am unfortunately ill, doing bare minimum now to unblock peeps. Will look if I can squeeze this one in too |
Wishing you a speedy recovery! 🌟 |
created draft for the app Pr to add the new property |
Started with the App PR |
Web PR is up too |
No need for Auth changes its already there |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.42-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-02-26. 🎊 For reference, here are some details about the assignees on this issue:
|
Issue is ready for payment but no BZ is assigned. @twisterdotcom you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
Payment Summary
BugZero Checklist (@twisterdotcom)
|
not able to access the above thread is it for me @twisterdotcom ? |
Ah sorry @ishpaul777 no. I was querying in Slack what the price was here, looks like we're going with $500, so I'll send a contract over in a mo. |
Sent and updated the Payment Summary. |
Accepted! Thanks @twisterdotcom |
Paid! |
Problem
Part of #36171
The
policy. isTaxTrackingEnabled
property does not exist in this shape in our policy data in database. Its saved aspolicy.tax.trackingEnabled : boolean
. Given we are updating how the policy changes are being saved and propagated to the clients, its cleaner to keep this structure same in Onyx as well. Having different code and different data schema throughout the stack results in less straightforward, more confusing, and more bug prone codeSolution
Update the Policy schema and usage of the
policy.isHarvestingEnabled
property to expect this data inpolicy.tax.trackingEnabled : boolean
format. Update the backend API to also return the data in this shape.Steps:
policy.tax.trackingEnabled
is not available, fallback topolicy. isTaxTrackingEnabled
in the mean timepolicy.tax.trackingEnabled
policy.isTaxTrackingEnabled
from the AppUpwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: