-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
[Bounty] A bunch of bugs that can be completed through the Bounty program #1012
Comments
I would like to work on this issue within the Bounty Program. |
A pleasure. Assigned to you @aeworxet |
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.Third-party contributors should coherently articulate how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue. |
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. |
❌ @ramishj is not authorized to use the Bounty Program's commands. |
No PRs have been submitted yet; a code investigation is ongoing. |
To lay the foundation for fixing #980, PR stoplightio/spectral#2658 was submitted to https://github.com/stoplightio/spectral, so the Timeline of this Bounty Issue is frozen until that PR is merged. |
PR stoplightio/spectral#2658 was merged in one day, so the Timeline of this Bounty Issue is resumed from the same point. |
AsyncAPI Maintainer (@jonaslagoni) delayed response for one period of three consequent working days 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. |
Update
|
UPDATE
|
PR asyncapi/studio#1126 with the final fix of #936 for |
Response, critical for technical resolution of this Bounty Issue (review of the PR) was delayed for one period of three consecutive working days so all remaining target dates of the Bounty Issue's Timeline are extended by two calendar weeks. 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. |
The last PR for this Bounty Issue was merged on 2024-08-14, and since that time I'm waiting for confirmation of the technical resolution of this Bounty Issue. |
I confirm the issue is solved now. |
Bounty Issue Is Completed 🎉@aeworxet, please go to the AsyncAPI page on Open Collective and submit an invoice for |
SUMMARY
|
Describe the bug
The completion of all of the following bugs can be considered as completing a single Bounty Program issue of
medium
complexity level :range
Values in Error Diagnostics for Different AsyncAPI File Formats #936The text was updated successfully, but these errors were encountered: