William Cheng

@ackintosh thanks for the PR. Ruby API client actually follows this approach but the majority of the generators use the current PHP approach. I'm not sure which one is better...

thanks for the pr closed via https://github.com/OpenAPITools/openapi-generator/pull/22174 with resolved merge conflicts

> I guess you could add a tag Default to all of your paths, and then they'd be incorporated into the same generated interface. FYI. There's a normalizer rule called...

i think this line: https://github.com/OpenAPITools/openapi-generator/blob/7a7c8c19ab66c2f0d54842c0945ed675cc114b1e/modules/openapi-generator/src/main/resources/Java/libraries/okhttp-gson/README.mustache#L93 can you please file a PR with the suggested fix? Edit: and this one as well https://github.com/OpenAPITools/openapi-generator/blob/7a7c8c19ab66c2f0d54842c0945ed675cc114b1e/modules/openapi-generator/src/main/resources/Java/libraries/okhttp-gson/api_doc.mustache#L29

> This PR added new additionalProperty "methodNamingConvention" to handle special cases with mutiple properties like "test" and "_test" which will end in the same getter and setter "getTest" thanks for...

2 suggestions: 1) merge the latest master to this branch to fix the build errors 2) instead of adding a new option, copy the `modelPropertyNaming` option from some other generators...

thanks for the PR, which has been merged sorry for the delay.

yes can you please file a PR accordingly to update the mustache template for the auto-generated documentation?

Thanks for the PR but your commit (as shown in the Commits tab) is not linked to your Github account, which means this PR won't count as your contribution in...

https://github.com/OpenAPITools/openapi-generator-cli/pull/801 filed by @tomarad please review when you guys have time