Skip to content

#25529: Fixed the wrong condition to output "Shipping Method Title" #25530

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 2 commits into from
Nov 25, 2019

Conversation

andrewbess
Copy link
Contributor

Description (*)

The wrong condition to output "shipping method title" in Magento_Checkout/js/view/summary/shipping

return shippingMethod ?
shippingMethod['carrier_title'] + shippingMethodTitle :
shippingMethod['carrier_title'];

What can happen if shippingMethod will not be an array?

Fixed Issues (if relevant)

  1. Wrong program code in "Magento/Checkout/view/frontend/web/js/view/summary/shipping.js" #25529: Wrong program code in "Magento/Checkout/view/frontend/web/js/view/summary/shipping.js"

Manual testing scenarios (*)

  1. Set shipping method as type "string" in the quote like a quote.shippingMethod('test') before shippingMethod = quote.shippingMethod();
  2. Check the sidebar on step 2
  3. Shipping shouldn't look javascript type "undefined" Incorrect delivery display

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

"Magento/Checkout/view/frontend/web/js/view/summary/shipping.js"

- added additional checking of shippingMethod type - need to be an array
- fixed condition to output "shipping method title"
@andrewbess andrewbess requested a review from DrewML as a code owner November 8, 2019 14:42
@m2-assistant
Copy link

m2-assistant bot commented Nov 8, 2019

Hi @andrewbess. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Guide documentation.

@VladimirZaets VladimirZaets added the Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests label Nov 8, 2019
@ghost ghost assigned VladimirZaets Nov 8, 2019
@magento-engcom-team magento-engcom-team added Partner: Atwix Pull Request is created by partner Atwix partners-contribution Pull Request is created by Magento Partner labels Nov 8, 2019
"Magento/Checkout/view/frontend/web/js/view/summary/shipping.js"

- fixed condition for shippingMethod
@engcom-Alfa
Copy link
Contributor

Hi @VladimirZaets, Could you review the latest commit?
Thanks!

@magento-engcom-team
Copy link
Contributor

Hi @VladimirZaets, thank you for the review.
ENGCOM-6256 has been created to process this Pull Request

@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

@m2-assistant
Copy link

m2-assistant bot commented Nov 25, 2019

Hi @andrewbess, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@magento-engcom-team magento-engcom-team added this to the Release: 2.3.5 milestone Nov 25, 2019
@andrewbess andrewbess deleted the issue-25529 branch October 28, 2020 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Award: bug fix Component: Checkout Partner: Atwix Pull Request is created by partner Atwix partners-contribution Pull Request is created by Magento Partner Progress: accept Release Line: 2.3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants