Enable reusability of schemas between versions

[jonaslagoni]

Reason/Context

There are specifically 2 schemas we wish to share among all versions.

• avroSchema_v1
• openapiSchema_3_0

To achieve this we need to do the following:

1. Move the common schemas to a common definition folder
2. Adapt the bundler (tools/bundler/index.js) to include these common definitions for all versions.

[achiverram28]

I would like to work on this

[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]

/gfi

[asyncapi-bot]

Hey @jonaslagoni, your message doesn't follow the requirements, you can try /help.

[jonaslagoni]

/help

[asyncapi-bot]

Hello, @jonaslagoni! 👋🏼

I'm 🧞🧞🧞 Genie 🧞🧞🧞 from the magic lamp. Looks like somebody needs a hand!

At the moment the following comments are supported in issues:

• /good-first-issue {js | ts | java | go | docs | design | ci-cd} or /gfi {js | ts | java | go | docs | design | ci-cd} - label an issue as a good first issue.
  example: /gfi js or /good-first-issue ci-cd

[jonaslagoni]

/gfi js

[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 ❤️

[devilkiller-ag]

Hi @jonaslagoni, is this issue still unresolved? Also while going through the tools/bundler/index.js file, I found some repetitive spelling mistakes in code comments.

[jonaslagoni]

Still a problem yea, feel free to grab it 🤙

[devilkiller-ag]

Hi @jonaslagoni, Just to be clear, I need to first move these files from definitions/v3.0.0 to a new folder definitions/common and then update the loadDefinitions function in tools/bundler/index.js accordingly?

[jonaslagoni]

Sounds about right yea @devilkiller-ag 👍

[AnimeshKumar923]

what's the status of this one? @jonaslagoni @devilkiller-ag

[devilkiller-ag]

Hi @AnimeshKumar923 I am sorry, I forgot this one. I will complete this in the upcoming week as I am currently on vacation.

[Shahbaz898414]

Hi @jonaslagoni, is this issue still unresolved?

[jonaslagoni]

@Shahbaz898414 its being worked on yes

[asyncapi-bot]

🎉 This issue has been resolved in version 6.5.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀