https://github.com/asyncapi/parser-go

[gedw99]

Trying to understand why https://github.com/asyncapi/parser-go is not used in this project ?

Would like to know so I understand objectives a bit more and basic ally just curious why its not used.

https://github.com/c0olix/asyncApiCodeGen/blob/main/generator/generator.go does use it and is a project that has similar goals to this one.

[gedw99]

I presume that https://github.com/lerenn/asyncapi-codegen/blob/main/examples/helloworld/v3/asyncapi.yaml conforms and could be parsed by https://github.com/asyncapi/parser-go ?

[lerenn]

Hello @gedw99 !

There is several reason that this repository is not used anymore in this project:

• When I started this project, I didn't know it existed, so I just checked AsyncAPI specs as best as I could
• Then I saw this project, I used it to just check that asyncapi spec were okay (here is where it was used: https://github.com/lerenn/asyncapi-codegen/blob/7995a54eaeab1c5b612ac53039d0ad2bdb1d5c29/pkg/codegen/parse.go)
• Someone asked for the support of asyncapi V3, which was not supported by parser-go, so I just duplicated my work for the v2 and made some changes for v3 and continued my work to check on my side but it's not perfect.

So as soon as v3 is supported, we can add this project again to check v3 versions :)

[lerenn]

presume that https://github.com/lerenn/asyncapi-codegen/blob/main/examples/helloworld/v3/asyncapi.yaml conforms and could be parsed by https://github.com/asyncapi/parser-go ?

Yes, except if I did an error, it should be conform

[gedw99]

thanks @lerenn

All makes sense. Looking forward to V3 support.