-
Notifications
You must be signed in to change notification settings - Fork 12
[150] Asynchronously process transaction backfills #195
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
[150] Asynchronously process transaction backfills #195
Conversation
44fabcf
to
d8817f5
Compare
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.
Looks like we may need to update a couple of specs here as a result of moving this process to async.
app/jobs/super_good/solidus_taxjar/backfill_transaction_sync_batch_job.rb
Show resolved
Hide resolved
@@ -2,11 +2,10 @@ | |||
|
|||
RSpec.describe SuperGood::SolidusTaxjar::BackfillTransactions do | |||
describe ".call" do |
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.
I know it's not in this PR but this should be describe "#call" do
because it's an instance method. That being said since we aren't passing anything to the initializer anymore it could also just be a class method instead.
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.
Addressed!
8e8e641
to
816b91a
Compare
d8817f5
to
56f0af1
Compare
Sorry just a rebase on master since the base branch was merged! No changes yet |
56f0af1
to
2b493fb
Compare
Tests still need some attention, but otherwise |
2b493fb
to
9130fe3
Compare
Just a push to fix the tests! |
9130fe3
to
e8a6b60
Compare
60c5cc1
to
beeec8a
Compare
This variable is no longer needed for test setup and can be removed. Co-authored-by: Nick Van Doorn <[email protected]>
Transaction backfills have the potential to encompass a large number of orders, so we should execute them asychronously, and direct the user to the in progress batch display page. Co-authored-by: Nick Van Doorn <[email protected]> Co-authored-by: Chris Todorov <[email protected]>
The ID of the transaction sync batch can change when the whole suite is run on CI, so we should just check for a number regex instead of a hardcoded number.
beeec8a
to
15c1e9f
Compare
What is the goal of this PR?
Transaction backfills have the potential to encompass a large number of orders, so we should execute them asychronously, and direct the user to the in progress batch display page.
How do you manually test these changes? (if applicable)
Merge Checklist