Visual Designer: Message schema

[Amzani]

Add the schema into the design system

@fmvilas already did it in the past - we can reuse some of his stuffs here.

Related to #748

[fmvilas]

To clarify: I can't contribute what I did in the past because it's proprietary code. Happy to give feedback though.

[aeworxet]

Bounty Issue's service comment

Text labels: bounty, bounty/2024-Q1, level/advanced, bounty/coding
First assignment to third-party contributors: 2023-12-23 00:00:00 UTC+12:00
End Of Life: 2024-05-31 23:59:59 UTC-12:00

[fmvilas]

Assigning this bounty to @princerajpoot20 🙌

[aeworxet]

Bounty Issue's Timeline

Complexity Level	Assignment date (by GitHub)	Start date (by BP rules)	End date (by BP rules)	Draft PR submission	Final PR submission	Final PR merge
Advanced	2023-12-18	2024-01-01	2024-02-23	2024-01-19	2024-02-09	2024-02-23

Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.

[aeworxet]

@asyncapi/bounty_team

[aeworxet]

@princerajpoot20, please provide an update to the PR.

[princerajpoot20]

Update

• I've created a draft PR.
• The transition from the Code editor to the Visual editor is complete.
• A few fixes need to be done in the visual editor part.

This week:

• The add property option is now functional for inner objects as well.

Currently working on:

• I am working on resolving type error that is causing the build to fail, though it runs on my local machine.

[aeworxet]

I'm looking at the Commits section of the PR when I check for an update. The last commit in the Commits section is Jan 19, 2024, while last Friday was Jan 26, 2024, and that's why I pinged.

Changes in the Commits section of the PR show that the work is ongoing and the issue is not dropped; that's why it is used as an indicator.

[princerajpoot20]

Hello Everyone.

I want to request an extension for this bounty issue.
I have been busy with my exams, so I have not been able to work efficiently for the past few weeks. I would really appreciate it if the deadline could be extended by 3 weeks.

Thank you.

cc @fmvilas @Amzani @aeworxet

[fmvilas]

That looks good to me 👍 I hope you did great in your exams mate.

[aeworxet]

Bounty Issue's Timeline Extended

Complexity Level	Assignment date (by GitHub)	Start date (by BP rules)	End date (by BP rules)	Draft PR submission	Final PR submission	Final PR merge
Advanced	2023-12-18	2024-01-01	2024-03-15	2024-01-19	2024-03-01	2024-03-15

Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.

[fmvilas]

Since I'm a bit busy lately, @Amzani will be replacing me in helping and guiding @princerajpoot20 to complete it. I'm not disappearing though, still here if you require something from me.

[Amzani]

Thanks for updating the timeline @aeworxet

[Amzani]

@princerajpoot20 completed the majority of work, but it's not 100% functional and still needs to be refined.
The extension will not solve the issue, as he will be busy for the remaining weeks with Exams and GSoC.

I propose to downgrade this Bounty Issue to medium, merge it as is (as it's not production - only Design system work for the new studio), and submit the second iteration that will be taken by @princerajpoot20 or another contributor, also as a medium issue.

[aeworxet]

Upon request of the AsyncAPI Maintainer, who is responsible for the resolution of the Bounty Issue from the AsyncAPI's side (@Amzani), the Complexity Level of this Bounty Issue has been reclassified to Medium.

[aeworxet]

After reclassification of the Bounty Issue to Medium and resolution of the technical delay with merge of the PR, which was beyond the control of the Bounty Program Participant,

Bounty Issue Completed 🎉

@princerajpoot20, please go to the AsyncAPI page on Open Collective and submit an invoice for USD 200.00 with the expense title Bounty studio#755, tag bounty, and full URL of this Bounty Issue in the description.