Add fqn_for_swagger_name option

[hypnoce]

Problem :
Name generation can output unreadable concatenation. It is also dependent on the unicity, which can completely change the documentation by adding one message. It is a big side effect.

To have a more repeatable name generation as well as to ensure unicity and readability, generate swagger name as a dot-separated concatenation for proto fully qualified name.

Can help fix #877

[johanbrandhorst]

Nice work, complete with tests and all 😍! I'm just wondering, have you explored what the standard way of namespacing things is in the OpenAPI/swagger world? It might be we might want to do a little research before merging this to see if there's another alternative representation that might be better. In any case, this is a backwards-compatible change so I have no real objections.

[hypnoce]

Indeed, always trying to keep things backward compatible.
Let me research things to see if we can have a more 'swagger' way of namespacing.

[hypnoce]

Hi,

after some search, the only thing that is the closest to package/namespace if the xml namespace/prefix. Also, the swagger code gen has a specific option for generated package : https://github.com/swagger-api/swagger-codegen/tree/master/modules/swagger-codegen-maven-plugin. I believe their is no good support for namespaces/package in openapi 2 (as well as 3)

Thanks !

[johanbrandhorst]

SGTM, thanks for this!