Skip to content

Fix Swagger output - update operation parameter "name" when parameter "in" is "body" #7432

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

Closed
wants to merge 1 commit into from
Closed

Fix Swagger output - update operation parameter "name" when parameter "in" is "body" #7432

wants to merge 1 commit into from

Conversation

careys7
Copy link
Member

@careys7 careys7 commented Nov 15, 2016

This was previously being output as a string "$body" which appears to have been a workaround for a now-fixed swagger-codegen bug PR 630. The convention appears to be name "body" when using in "body" elsewhere.

Other parameters in Magento's swagger file are not prefixed with a dollar sign. Removing this would also prevent variable variable assignments when using php-based Swagger / Open API code generators like janephp/openapi.

…rameter "in" is "body"

This was previously being output as a string "$body" which appears to have been a workaround for a now-fixed swagger-codegen bug (#630). The convention appears to be name "body" when using in "body" elsewhere.

Other parameters in Magento's swagger file are not pre-fixed with a dollar sign. Removing this would prevent variable variable assignments when using php-based Swagger / Open API code generators like janephp/openapi.
@magento-cicd2
Copy link
Contributor

magento-cicd2 commented Nov 15, 2016

CLA assistant check
All committers have signed the CLA.

@careys7 careys7 changed the title Updated Swagger output to fix operation parameter name output when parameter "in" is "body" Fix Swagger output - update operation parameter "name" when parameter "in" is "body" Nov 15, 2016
@careys7 careys7 closed this Nov 15, 2016
@careys7
Copy link
Member Author

careys7 commented Nov 16, 2016

Closed in favour of #7446 which includes user-friendly body-class naming if using a generated client.

magento-devops-reposync-svc pushed a commit that referenced this pull request Apr 12, 2022
…develop

AC-2218: Fixed problem when Magento updates from 2.2 to 2.3, next 2.4.4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants