studio
studio copied to clipboard
asyncapi
Enhance the Visual JSON Schema Editor
After merging: https://github.com/asyncapi/studio/pull/905 The visual editor needs to be enhanced for production
Scope
- [ ] Look & Feel
- [ ] Deletion
- [ ] Nested objects
- [ ] Test functionality
Complexity
Medium
Bounty Issue's service comment
Text labels: bounty/2024-Q2, bounty/medium, bounty/coding
First assignment to third-party contributors: 2024-03-22 00:00:00 UTC+12:00
End Of Life: 2024-08-31 23:59:59 UTC-12:00
@asyncapi/bounty_team
@koukama
Please specify your real name in your GitHub profile as per your passport/ID before participating in the Bounty Program, as it will be compared to the Legal Name / Full name of the account holder during the payout.
https://github.com/asyncapi/community/pull/897/files#diff-25ecb20a61754c225d6511ca08d7e7c9a14b9ca5a93e89bd42331e51c9ebf26dR186
As @princerajpoot20 is currently busy and you seem interested in continuing his work please go ahead @koukama. In case you need more context feel free to coordinate with @princerajpoot20.
@princerajpoot20 i will like to work on it if no one is working on it. Thanks
Details about the Tasks
Things to Implement
- Delete Property Function
- Toggle Required/NotRequired Function
- Change Type of Property Function
- Add Property function, but only for cases which have a path containing
array<object>. - UI look and feel according to the Figma design.
Some minor fixes:
- When a property is of the type
array, the data type of the array is not displayed in the visual editor.
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 |
|---|---|---|---|---|---|---|
| Medium | 2024-04-02 | 2024-04-08 | 2024-05-17 | 2024-04-19 | 2024-05-03 | 2024-05-17 |
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.
@utnim2 Let me know if you need any help.
Hey @princerajpoot20 the figma link is broken in #748
@utnim2 the link is Ok. I think something is wrong with Figma. first login Figma and then clink on that link. it should work. If that didn't help, you can try using this link
Upon request of the Bounty Program Participant (@utnim2), all remaining target dates of the Bounty Issue's Timeline are extended by one calendar week.
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 |
|---|---|---|---|---|---|---|
| Medium | 2024-04-02 | 2024-04-08 | 2024-05-24 | 2024-04-19 | 2024-05-10 | 2024-05-24 |
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 Could you please extend the deadline by two weeks? There are some changes left to be implemented by @Gmin2. Thank you for the consideration. 🙂
Upon request of the AsyncAPI Maintainer, who is currently leading the development (@princerajpoot20), all remaining target dates of the Bounty Issue's Timeline are extended by two calendar weeks.
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 |
|---|---|---|---|---|---|---|
| Medium | 2024-04-02 | 2024-04-08 | 2024-06-07 | 2024-04-19 | 2024-05-10 | 2024-06-07 |
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.
Bounty Issue Completed 🎉
@Gmin2, please go to the AsyncAPI page on Open Collective and submit an invoice for USD 200.00 with the expense title Bounty studio#1023, tag bounty, and full URL of this Bounty Issue in the description.
@Bhavyajain21
There is a Slack Workspace. You can find most people in it by their GitHub handles or names.