-
Notifications
You must be signed in to change notification settings - Fork 6k
PHP Namespace Is Not API-Specific #974
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
Comments
@andrewmunsell may I know if you've tested the PHP client in the
and here is the available option in the config.json
|
I have filed a PR to fix this here: #977 |
Thanks @who. The PR has been merged into @andrewmunsell please test to see if you're happy with the latest PHP client in |
@andrewmunsell we're closing this issue since we've not heard from you. Please open a new one if needed. |
Right now, the generated PHP client SDK uses a generic namespace (
SwaggerClient
) and generic class names for some of the classes (Configuration
, for example). This could cause conflicts if multiple Swagger based API SDKs were included in a single project.The namespace of the generated API SDKs should be specific to the API itself, either generated automatically from the API name, or specified manually.
The text was updated successfully, but these errors were encountered: