-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[API][PaymentRequest] Rename payment request operations for shop context #18568
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
Conversation
WalkthroughPayment request API operation identifiers were renamed from generic "show" to shop-specific "shop" names and an upgrade note for 2.1.8 documenting the mapping was added to upgrade documentation. No behavioral or payload changes were introduced. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes
Suggested labels
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
❌ Preview Environment deleted from BunnyshellAvailable commands:
|
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.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
UPGRADE-API-2.1.md(1 hunks)src/Sylius/Bundle/ApiBundle/Resources/config/api_platform/resources/shop/PaymentRequest.xml(3 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
UPGRADE-API-2.1.md
3-3: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🔇 Additional comments (4)
src/Sylius/Bundle/ApiBundle/Resources/config/api_platform/resources/shop/PaymentRequest.xml (3)
22-24: Clean rename of GET operation to shop naming convention.The operation identifier correctly follows the shop API naming pattern. All other operation metadata (URI template, normalization context) remains unchanged.
38-40: Clean rename of POST operation to shop naming convention.The operation identifier is correctly updated. The operation's URI template, input command, and normalization/denormalization contexts remain intact.
79-81: Clean rename of PUT operation to shop naming convention.The operation identifier is correctly updated to the shop naming pattern. The provider, input command, and all context groups remain unchanged.
UPGRADE-API-2.1.md (1)
7-11: Migration table accurately documents the renamed routes.The old→new route mappings correctly correspond to the operation name changes in PaymentRequest.xml (lines 22, 38, 79). The table format is clear and follows the upgrade documentation convention.
GSadee
left a comment
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.
Payment requests are still experimental, so I believe we can change this without breaking BC Policy, but I would be in favour of doing that in version 2.2, because it is a change that may affect the end application. Wdyt?
This PR renames payment request API operations to follow the shop API naming convention.
Changes:
sylius_api_show_payment_request_gettosylius_api_shop_payment_request_getsylius_api_show_payment_request_posttosylius_api_shop_payment_request_postsylius_api_show_payment_request_puttosylius_api_shop_payment_request_putThis standardizes the naming convention for shop context payment request operations. Since the PaymentRequest component is experimental, these route renames are considered acceptable.
Ref: #18439