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

Update code to reduce redundancy and simplify readability #28608

Merged
merged 8 commits into from
Aug 8, 2020

Conversation

df2k2
Copy link
Contributor

@df2k2 df2k2 commented Jun 8, 2020

Simplified code complexity by optimizing logic, redundant variable assignments, over-usage of returns within a function. Eliminated needless and redundant variable assignment.

Description (*)

Simplifying logic and readability randomly

Manual testing scenarios (*)

  1. Modified functions are simpler yet do not change any logic within lib/internal/Magento/Framework/App/Request/Http.php

Questions or comments

No.

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)

Resolved issues:

  1. resolves [Issue] Update code to reduce redundancy and simplify readability #29381: Update code to reduce redundancy and simplify readability

@m2-assistant
Copy link

m2-assistant bot commented Jun 8, 2020

Hi @df2k2. 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.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

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

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

Copy link
Contributor

@lbajsarowicz lbajsarowicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your contribution. Please review my Code Review comments.

Copy link
Contributor Author

@df2k2 df2k2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

@df2k2 df2k2 requested a review from lbajsarowicz June 12, 2020 12:59
@lbajsarowicz
Copy link
Contributor

@magento run all tests
Good afternoon @df2k2 , I'm running tests to make sure that everything works fine with your PR. If there are no issues, I am going to approve your changes and soon, all the changes should be processed by Core Team.

@lbajsarowicz
Copy link
Contributor

@magento run Functional Tests CE

Looks like the failing test is flaky one. Trying to re-run it and in the meantime, I'm accepting the PR.

Copy link
Contributor

@lbajsarowicz lbajsarowicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✔️ Thank you for your contribution!

@magento-engcom-team
Copy link
Contributor

Hi @lbajsarowicz, thank you for the review.
ENGCOM-7680 has been created to process this Pull Request
✳️ @lbajsarowicz, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@VladimirZaets VladimirZaets added Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Jun 18, 2020
@engcom-Delta engcom-Delta self-assigned this Jul 7, 2020
@engcom-Echo
Copy link
Contributor

@magento run all tests

Copy link
Contributor

@lbajsarowicz lbajsarowicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✔️ Thanks for your input.

@magento-engcom-team
Copy link
Contributor

Hi @lbajsarowicz, thank you for the review.
ENGCOM-7680 has been created to process this Pull Request
✳️ @lbajsarowicz, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@engcom-Alfa
Copy link
Contributor

engcom-Alfa commented Aug 4, 2020

@lbajsarowicz Could you put an appropriate label for test coverage?
Thanks!

@lbajsarowicz lbajsarowicz added the Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests label Aug 4, 2020
@lbajsarowicz
Copy link
Contributor

@engcom-Alfa This class is one of the most-covered ones, that is the result of the dependencies relying on this class.

@engcom-Alfa
Copy link
Contributor

✔️ QA Passed
Was checked general cases ( create orders as guest and customer, register new customer, wishlist, and compare products) and everything works as expected.

@engcom-Alfa
Copy link
Contributor

@magento create issue

@engcom-Alfa engcom-Alfa added QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope and removed QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) labels Aug 4, 2020
@magento-engcom-team magento-engcom-team merged commit 3c65835 into magento:2.4-develop Aug 8, 2020
@m2-assistant
Copy link

m2-assistant bot commented Aug 8, 2020

Hi @df2k2, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Component: App Priority: P3 May be fixed according to the position in the backlog. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

[Issue] Update code to reduce redundancy and simplify readability
7 participants