Add Guidance for Code Generation

[sebbader-sap]

The OpenAPI files are usually not manually translated into executable code but through the help of code generators. We are aware that some work pretty well, others somehow, and then there is a number of generators which just produce nonsense - if at all. We should add a section explaining the current state as far as we are aware of it, and document known issues and maybe even recommend one or two alternatives for the most important use cases.

Furthermore:

• the AAS community will not support anything, that's in the responsibility of the generator communities
• the described state might only be valid for very defined versions of the API and the generators --> the community as a whole needs to work together to keep the descriptions up to date.

[sebbader-sap]

Let's prepare an answer in this branch: https://github.com/admin-shell-io/questions-and-answers/tree/95-code-generation

[sebbader-sap]

@alexgordtop @noheton please add your findings as well.

[StenGruener]

ping @sebbader-sap ready to merge?

[sebbader-sap]

Hi Sten, doesn't look like anything has changed since July :-).

@alexgordtop @noheton can you please add your findings in the mentioned branch?

[StenGruener]

@alexgordtop @noheton ping

[StenGruener]

@sebbader-sap @alexgordtop @noheton ping

[sebbader-sap]

I am not using any code generators for OpenAPI. Can anyone who does give a few insights?

[sebbader-sap]

Did anything change in the meantime? Did the generators become better, for instance?

[StenGruener]

no updates from participants, closing for now. @sebbader-sap feel free to re-open once you get new insights