Skip to content
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

Re-apply fix for JS error in the customer data #36177

Merged
merged 11 commits into from
Mar 2, 2023

Conversation

TuVanDev
Copy link
Member

@TuVanDev TuVanDev commented Sep 22, 2022

Description (*)

The fixes for issue #31920 in PR 31940 were removed accidentally. This PR revert code changes in PR 31940 for fixing errors in customer data when component is not initialized.

Related Pull Requests

Related Commits

Fixed Issues (if relevant)

  1. Fixes JS error in the customer data #31920

Manual testing scenarios (*)

  1. ...
  2. ...

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)

Revert code changes for fixing errors in customer data when component is not initialized - accident removed in a previous commit
@m2-assistant
Copy link

m2-assistant bot commented Sep 22, 2022

Hi @Viper9x. Thank you for your contribution
Here are 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.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

For more details, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@TuVanDev
Copy link
Member Author

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@TuVanDev
Copy link
Member Author

@magento run Functional Tests B2B,Functional Tests CE,Functional Tests EE,Unit Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@sdzhepa sdzhepa added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Sep 22, 2022
@TuVanDev
Copy link
Member Author

@magento run Functional Tests B2B,Unit Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@TuVanDev
Copy link
Member Author

@magento run Functional Tests B2B,Unit Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@TuVanDev
Copy link
Member Author

@magento run Unit Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@TuVanDev
Copy link
Member Author

@magento run Unit Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@TuVanDev
Copy link
Member Author

@magento run Unit Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@TuVanDev
Copy link
Member Author

@magento run Unit Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@TuVanDev
Copy link
Member Author

@magento run Unit Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@TuVanDev
Copy link
Member Author

@magento run Unit Tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@TuVanDev
Copy link
Member Author

@magento run all tests

@mrtuvn
Copy link
Contributor

mrtuvn commented Feb 10, 2023

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@AshishKumarPundeer
Copy link
Contributor

AshishKumarPundeer commented Feb 15, 2023

@Viper9x @ihor-sviziev
Thanks for the collaboration & contribution!

✖️ QA Failed

Re-apply fix for JS error in the customer data

Manual Scenario Steps

  1. After taking the PR changes we have checked the issue got fixed. But for the scenario we are still able to reproduce the same. Please find the attached screenshot for you references.

Before taking the PR changes
Screenshot 2023-02-15 at 7 54 04 PM

After taking the PR changes
Screenshot 2023-02-15 at 8 08 54 PM

@engcom-Charlie engcom-Charlie self-assigned this Feb 15, 2023
@engcom-Charlie
Copy link
Contributor

As per this comment, moving it to Changes Requested.

Thank you!

@ihor-sviziev
Copy link
Contributor

ihor-sviziev commented Feb 16, 2023

So looks like if we can't accept these changes, we should always wrap our code in

customerData.getInitCustomerData().done(function () {
    // .. my code there
});

@AshishKumarPundeer
Copy link
Contributor

@ihor-sviziev and @Viper9x we are working on mentioned failure.

Thank you

@engcom-Charlie
Copy link
Contributor

Pushed the code fix for mentioned issue on behalf of @AshishKumarPundeer

Thank you!

@AshishKumarPundeer
Copy link
Contributor

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@AshishKumarPundeer
Copy link
Contributor

@magento run Functional Tests EE

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@AshishKumarPundeer
Copy link
Contributor

@magento run Functional Tests EE

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@AshishKumarPundeer
Copy link
Contributor

Functional Tests EE failures are different on last two run
Run1
Screenshot 2023-02-23 at 12 29 01 PM

Run2
Screenshot 2023-02-23 at 12 29 06 PM

Hence moving to further process

@engcom-Charlie
Copy link
Contributor

Hi @Viper9x and @ihor-sviziev,

Thank you for the contribution!

I have tested the issue with the PR changes and it’s working fine . Also the above mentioned regression is not occurring now.

✔️ QA Passed

Steps to reproduce

  1. Add the following code to the page on frontend:
<script>
    require(['Magento_Customer/js/customer-data'], function (customerData) {
        console.log(customerData.getExpiredSectionNames());
    });
</script>
  1. Visit the storefront, check the console

Before: ✖️
image

After: ✔️
image

  1. "mage-cache-storage" cookie expiration date is now getting updated after "Cookie Lifetime" is changed.
    image

As the PR is now working as expected, moving it to Merge in Progress.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept
Projects
Status: Recently Merged
Development

Successfully merging this pull request may close these issues.

JS error in the customer data