forked from OpenStackweb/summit-admin
-
Notifications
You must be signed in to change notification settings - Fork 4
fix: redirect cart payment to purchase details #964
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
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.
🧩 Analysis chain
🏁 Script executed:
Repository: fntechgit/summit-admin
Length of output: 523
🌐 Web query:
OpenStack Purchases API payment confirmation response format💡 Result:
I couldn’t find any “OpenStack Purchases API” (or any OpenStack service/API endpoint with a “Purchases” resource that includes a payment-confirmation response format) in the official OpenStack documentation set. The OpenStack API reference index lists many OpenStack projects/services (Nova, Cinder, Neutron, etc.) but nothing named “Purchases API” or payment-confirmation for purchases [1]. The closest official “OpenStack API” content I found relates to compute (Nova) request/response formats, not purchases or payment confirmation [2]. What I did find: several third-party platforms use the word “purchases” and define their own “payment confirmation/resp-pay-confirmation” webhook response formats (not OpenStack). For example, EnKash defines a payment confirmation response schema with fields like payload, response_code, and response_message [3]. If you meant a specific marketplace/billing platform that “integrates with OpenStack” (e.g., Waldur marketplace orders backed by OpenStack), share the product/service name and the exact endpoint path or repository so I can locate the precise response format. The OpenStack core documentation alone doesn’t appear to define such an API [1].
Citations:
🏁 Script executed:
Repository: fntechgit/summit-admin
Length of output: 2836
🏁 Script executed:
Repository: fntechgit/summit-admin
Length of output: 2105
🏁 Script executed:
Repository: fntechgit/summit-admin
Length of output: 4387
🏁 Script executed:
Repository: fntechgit/summit-admin
Length of output: 3113
🏁 Script executed:
Repository: fntechgit/summit-admin
Length of output: 633
🏁 Script executed:
Repository: fntechgit/summit-admin
Length of output: 13677
🏁 Script executed:
Repository: fntechgit/summit-admin
Length of output: 1545
🏁 Script executed:
Repository: fntechgit/summit-admin
Length of output: 3830
🏁 Script executed:
Repository: fntechgit/summit-admin
Length of output: 10228
🏁 Script executed:
Repository: fntechgit/summit-admin
Length of output: 892
🏁 Script executed:
Repository: fntechgit/summit-admin
Length of output: 244
🏁 Script executed:
Repository: fntechgit/summit-admin
Length of output: 7491
Critical:
confirmPayment()navigation likely uses the wrong purchase identifierpayment-view.jsnavigates withpurchase.purchase_id, but the purchases list UI routes purchase details withitem.id(history.push(${item.sponsor_id}/purchases/${item.id})), and repo usage consistently distinguishespurchases.idvspayments.payment_id.confirmPayment()just returns the rawresponsefrom the/payments/${paymentIntent.id}/confirmendpoint (no field mapping), so if that response usesid(notpurchase_id), this will push.../undefinedor the wrong purchase.Fix by aligning the field (
purchase.idvspurchase.purchase_id) to the actual/confirmresponse contract, and add a guard for a missing identifier.🤖 Prompt for AI Agents