fix(plugin-ecommerce): pass req to Payload API calls in Stripe adapter#15839
Merged
paulpopus merged 1 commit intopayloadcms:mainfrom Mar 4, 2026
Merged
Conversation
Contributor
Author
|
The single E2E failure ( |
paulpopus
approved these changes
Mar 4, 2026
Contributor
|
🚀 This is included in version v3.79.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What?
Adds the missing
reqparameter to allpayload.find(),payload.create(), andpayload.update()calls in the Stripe adapter'sconfirmOrder.tsandinitiatePayment.ts.Why?
Without
req, hooks on transactions/orders/carts receive an empty request context, and each database call runs in an isolated session — breaking transactional consistency (e.g. order created but cart not marked as purchased on failure).How?
Pass the existing
req(already available in scope) to each Payload API call. Also fixespayload.logger.errorcalls to use the correct object form per project conventions.Fixes #15836