Fix webapi returns variables in JSON using snake case and I need camelCase

[jayankaghosh]

Description (*)

Added objectKeyMap which accepts parameters from di.xml to modify data object keys
We can now modify the keys of any accessor on any class used in the rendering of the REST API, using the following (or similar) snippet in the di.xml of the webapi_rest directory.

<type name="Magento\Framework\Reflection\DataObjectProcessor">
        <arguments>
            <argument name="objectKeyMap" xsi:type="array">
                <item name="Magento\Cms\Api\Data\PageInterface" xsi:type="array"> <!-- Change the accessors keys of this class -->
                    <item name="page_layout" xsi:type="string">PageLayout</item> <!-- page_layout should be shown as PageLayout in the ouput -->
                </item>
            </argument>
        </arguments>
    </type>

Fixed Issues (if relevant)

1. Fixes webapi returns variables in JSON using snake case and I need camelCase #24681 : webapi returns variables in JSON using snake case and I need camelCase

Manual testing scenarios (*)

1. Add a di.xml inside webapi_rest directory of any module and inject object key names to it, similar to the following

<type name="Magento\Framework\Reflection\DataObjectProcessor">
        <arguments>
            <argument name="objectKeyMap" xsi:type="array">
                <item name="Magento\Cms\Api\Data\PageInterface" xsi:type="array">
                    <item name="page_layout" xsi:type="string">PageLayout</item>
                </item>
            </argument>
        </arguments>
    </type>

2. Call the REST API and observe the new keys reflecting.

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)

[m2-assistant]

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

[ihor-sviziev]

@magento run all tests

[ihor-sviziev]

Hi @jayankaghosh,
Thank you for your contribution! I'm really sorry that no one reviewed this PR earlier.

I'll take this PR and will provide my feedback soon.

From the first look - in general changes looks good to me, but some adjustments definitely will be required.

[ihor-sviziev]

Oh... I see that the branch from which was created this PR was already removed, so we basically can't accept this PR.

Unfortunately I have to close this PR due to that reason. If you're still interesting in contributing this improvement - please create a new PR with the same changes, I'll try to take it as fast as possible.

[m2-assistant]

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

[tuyennn]

@jayankaghosh could you create a new pull request base on current one.

[jayankaghosh]

@tuyennn Oh my. I forgot I've even made this PR. Lol.

Sure. I'll create a new PR at the earliest.

[jayankaghosh]

@ihor-sviziev @tuyennn Here's the new PR

#31001