Support converting to 3.0.0

[magicmatatjahu]

It's a long term feature request.

When we will have the 3.0.0 specification stabilized we should start writing functionality for converting versions 2.X.X to 3.0.0.

One of the problems I see are the external sources (local files and http links) which we are not converting at the moment but we should (see issue #90). In order not to cause problems for people and increase DX we should figure out a way to convert also external files in which messages (and other reusable components) can be defined.

Scope

• Convert 2.X.X to 3.0.0 #188
• Converter cannot handle reusability  #90
• Rewrite to TS #106
• Switch to Jest #107

[jonaslagoni]

handle reusable parts - #90

I will leave out this feature, for now, and introduce it later after v3. Cause it's a very tedious feature to get right, there are so many different combinations and weird scenarios you have to handle.

[asyncapi-bot]

🎉 This issue has been resolved in version 1.3.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀