Implement Python generator and renderers

[magicmatatjahu]

Implement Python generator and renderers like in TS or Java.

Generator should have possibility to define presets for class, enum type.

Additional: create presets for serialisation/converters from json.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

[joe-narvaez]

If we could get dataclass and/or pydantic support, that would be ideal.

[humbleengineer]

If we could get dataclass and/or pydantic support, that would be ideal.

Double thumbs up to that!

[derberg]

@damaru-inc hey, this one might be interesting for you. Since you created https://github.com/asyncapi/python-paho-template/ it means to me you are a good candidate to contribute here. Side effect is that later you can use Modelina in your template to generate some Python code

[jonaslagoni]

Tasklist to implement it:

• Duplicate one of the existing generators, for example, the Java generator, (I find it easier to start with that) https://github.com/asyncapi/modelina/tree/master/src/generators
• Start with empty generator options

  • modelina/src/generators/java/JavaGenerator.ts

    Line 17 in 57948b5

    export interface JavaRenderCompleteModelOptions {

  • modelina/src/generators/java/JavaGenerator.ts

    Line 13 in 57948b5

    export interface JavaOptions extends CommonGeneratorOptions<JavaPreset> {

• Adapt reserved keyword list to match it for python - https://github.com/asyncapi/modelina/blob/master/src/generators/typescript/Constants.ts
• Adapt the core PythonRenderer to render python types -

  modelina/src/generators/typescript/TypeScriptRenderer.ts

  Line 14 in 57948b5

  export abstract class TypeScriptRenderer extends AbstractRenderer<TypeScriptOptions, TypeScriptGenerator> {

• I find it easiest to start with two renders (those that call presets at specific times during the rendering process), one for Class and one of Enum.
• Adapt the code being generated for the Class and Enum to match Python.
• Start with no presets as we just start with the bare minimum.
• Adapt all releated docs.

For testing (yes we need tests 😄) I would again start by copying one of the existing test collections for a generator https://github.com/asyncapi/modelina/tree/master/test/generators/typescript and then remove anything that is not related to what you have in the Python generator.

@mahakporwal02 let me know if this makes sense 🙏

[mahakporwal02]

Tasklist to implement it:

• Duplicate one of the existing generators, for example, the Java generator, (I find it easier to start with that) https://github.com/asyncapi/modelina/tree/master/src/generators

• Start with empty generator options

  • modelina/src/generators/java/JavaGenerator.ts

    Line 17 in 57948b5

    export interface JavaRenderCompleteModelOptions {

  • modelina/src/generators/java/JavaGenerator.ts

    Line 13 in 57948b5

    export interface JavaOptions extends CommonGeneratorOptions<JavaPreset> {

• Adapt reserved keyword list to match it for python - https://github.com/asyncapi/modelina/blob/master/src/generators/typescript/Constants.ts

• Adapt the core PythonRenderer to render python types -

  modelina/src/generators/typescript/TypeScriptRenderer.ts

  Line 14 in 57948b5

  export abstract class TypeScriptRenderer extends AbstractRenderer<TypeScriptOptions, TypeScriptGenerator> {

• I find it easiest to start with two renders (those that call presets at specific times during the rendering process), one for Class and one of Enum.

• Adapt the code being generated for the Class and Enum to match Python.

• Start with no presets as we just start with the bare minimum.

• Adapt all releated docs.

For testing (yes we need tests smile) I would again start by copying one of the existing test collections for a generator https://github.com/asyncapi/modelina/tree/master/test/generators/typescript and then remove anything that is not related to what you have in the Python generator.

@mahakporwal02 let me know if this makes sense pray

Sure will look into it

[mahakporwal02]

Thanks @jonaslagoni 👍

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[jonaslagoni]

Solved in #863