-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AsyncAPI spec v3 support in Diff #154
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
cc codeowners @aayushmau5 @vinitshahdeo @onbit-uchenik @magicmatatjahu @derberg Would be really cool to have this library work out the gate when we release v3, are any of you interested in scheduling a public call specifically to discuss how to enable this? If you have any questions about how it can be achieved or v3-specific stuff I can help answer those in the meeting to enable you to progress with this 🙂 Let me know if it has any interest. |
@jonaslagoni I'll start working on this.
Sure! I haven't particularly kept up with the new spec changes, so it would be cool to get on a call and discuss the changes that needs to be made to this library. |
Cool! @aayushmau5 just let me know a date and time that fits for you and I can schedule a meeting 🙂 |
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 ❤️ |
Bounty Issue's service commentText labels: @asyncapi/bounty_team The Bounty Program is not a Mentorship Program. The accepted level of Bounty Program Participants is Middle/Senior.Regular contributors should explain in meaningful words how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue. |
Hi @jonaslagoni @aeworxet, |
@chinma-yyy i think it's best i work on this issue here. I already had some approach and some implementation done before this issue got stale. Will need to rework those so clubbed all the issues and will fix them on one go. |
@aayushmau5 is an AsyncAPI Maintainer specified in https://raw.githubusercontent.com/asyncapi/community/master/MAINTAINERS.yaml, so they fall under the first category in the prioritization list. |
Bounty Issue's Timeline
Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.Keep in mind the responsibility for violations of the Timeline. |
@aeworxet @aayushmau5 @jonaslagoni is this open...i would. like to work on this? |
@imabp I'm working on this issue :) |
Okay thanks for letting me know.. @aayushmau5 cc: @aeworxet |
@imabp Yeah, i had some work already done which got stale. I reopened it just now but yeah, i'm actively working on this issue. |
do you need any help? @aayushmau5 |
@imabp not yet. I'll let you know once I get these changes done. Maybe you can pick up other issues for diff if you want to :) |
Sure taking a look at them @aayushmau5 . I was developing Myer's Diff Algorithm, so had a chat with |
@aayushmau5 ( |
@aeworxet I'm done with adding support for asyncapi v3. I'm in the process of writing tests for the changes. |
@aayushmau5 ( |
2 similar comments
@aayushmau5 ( |
@aayushmau5 ( |
@aeworxet I'm currently going through AsyncAPI spec v3 and adding the proper standard file for it. |
@aayushmau5, are you on track to complete this Bounty Issue by 2024-12-01, or will you need an extension? |
I will be done with standard changes for diff. Will need an extension for updating diff for CLI |
Upon request of the AsyncAPI Maintainer, who is responsible for the resolution of the Bounty Issue from the AsyncAPI's side and is also the Bounty Program Participant (@aayushmau5 ( Bounty Issue's Timeline Extended
Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.Keep in mind the responsibility for violations of the Timeline. |
Reason/Context
This Issue is used to track changes needed to support AsyncAPI v3. As a code owner, please edit this list of TODO tasks in order to properly track the progress 🙂 Once this issue is closed it means that v3 is now fully supported in this library.
Remaining tasks:
The text was updated successfully, but these errors were encountered: