35937 internal server error in /v1/carts/mine/items api endpoint

[JettyRohanAditya]

Internal server error in /v1/carts/mine/items api endpoint

Description (*)

Second argument in array_key_exists($camelCaseKey, $currentArray) expects an array, but it's string here.
Added if clause to skip that.

Related Pull Requests

#35937

Fixed Issues (if relevant)

1. Fixes Internal Server Error in /V1/carts/mine/items API Endpoint #35937

Manual testing scenarios (*)

1. Retrieve auth token from the admin endpoint /V1/integration/admin/
2. Request endpoint:
   https://magento2.docker/index.php/rest/default/V1/carts/mine/items

Changes Made:-

Changed the code
From-
if (array_key_exists($camelCaseKey, $currentArray)) {
$lastKey = $camelCaseKey;
}
To -
if (is_array($currentArray)){
if (array_key_exists($camelCaseKey, $currentArray)) {
$lastKey = $camelCaseKey;
}
$currentArray[$lastKey] = $valueToSet;
}

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)

[m2-assistant]

Hi @JettyRohanAditya. Thank you for your contribution!
Here are some useful tips on 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 Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[Den4ik]

@JettyRohanAditya Please sign CLA

[JettyRohanAditya]

@magento run all tests

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run all tests

[engcom-Dash]

Hello @JettyRohanAditya,

Thanks for the collaboration & contribution!

✔️ QA Passed
Preconditions:

Install fresh Magento 2.4-develop
Steps to reproduce
According to the issue description.
Before: ✖️

After: ✔️

Builds are failed. Hence, moving this PR to Extended Testing.

Thanks

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run Unit Tests, Static Tests, Webapi Tests

[engcom-Dash]

@magento run Static Tests

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run Functional Tests B2B, Functional Tests EE

[engcom-Dash]

Moving this PR to 'Merge in Progress'.

[engcom-Dash]

@magento run Functional Tests EE

[engcom-Dash]

Moving this PR to 'Pending Review' as the changes have not yet been approved. Once the changes are approved, we will proceed further with it. Thank you for your understanding.