[Issue] Reduce async console logger

magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.

Open Software License 3.0

11.55k stars 9.32k forks source link

This issue is automatically created based on existing pull request: magento/magento2#33850: Reduce async console logger

Description (*)

Draft test path https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Ui/view/base/web/js/lib/logger/console-logger.js Out of curiousity do we actually need log always load at all page? Should have config allow we on/off load this or exclude it in production ?

Before this changes Home 187/219 js requests Category 190/223 js requests Details 209/250 js requests Checkout 317/389 js requests

After this changes Home 178/215 js requests Category 181/225 js requests Details 200/247 js requests Checkout 308/379 js requests

we no longer load around ~10 files. The best scenario not errors we have no longer load additional 10 files. But the worse case. When we got something goes wrong, we need log to indicate what problem and where it happen Functionals works without affected

No new update since 2017

cc: @VladimirZaets Can you give me some explain or related docs for this. Thanks you

Related Pull Requests

Fixed Issues (if relevant)

Fixes magento/magento2#

Manual testing scenarios (*)

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)
[ ] README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
[ ] All automated tests passed successfully (all builds are green)

Hi @engcom-Hotel. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
[ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop branch
Details
- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
[ ] 5. Add label Issue: Confirmed once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

magento / magento2