You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to generate classes for the Magento 2 schema JSON (which has other issues that need addressing within the schema itself), the versioning that Magento has applied to their API gets removed. I wonder if this should be supported in swagger-codegen?
For example: catalogAttributeSetRepositoryV1 gets converted to an API class of : CatalogAttributeSetRepositoryVApi. The classname CatalogAttributeSetRepositoryV1Api would be legal in PHP (just not if the first character of the class was a number).
Uh oh!
There was an error while loading. Please reload this page.
Description
Trying to generate classes for the Magento 2 schema JSON (which has other issues that need addressing within the schema itself), the versioning that Magento has applied to their API gets removed. I wonder if this should be supported in
swagger-codegen
?For example:
catalogAttributeSetRepositoryV1
gets converted to an API class of :CatalogAttributeSetRepositoryVApi
. The classnameCatalogAttributeSetRepositoryV1Api
would be legal in PHP (just not if the first character of the class was a number).Swagger-codegen version
2.2.2-SNAPSHOT
Swagger declaration file content or url
http://devdocs.magento.com/swagger/schemas/latest-2.0.schema.json
Command line used for generation
Using jimschubert/swagger-codegen-cli:
docker-compose.yml
:config.json
:Command:
Steps to reproduce
./swagger/config
,./swagger/schema
,./swagger/export
)./swagger/schema/schema.json
config.json
in./swagger/config/config.json
with contents shown aboveRelated issues
#2392 - [PHP] Invalid classes generated if models start with a digit.
Magento 2 - PR 7446 - addressing issue with schema generation.
Suggest a Fix
The text was updated successfully, but these errors were encountered: