-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
Visual Designer: Form component #752
Comments
This form should be generative right? I mean it should get a json schema and generate a form based on that. plus we could combine the AsyncAPI fields with binding to get a comprehensive list of editable properties. |
/progress 10
|
@KhudaDad414 I recommend going with the static approach to have more control customisation of form inputs. |
/progress 10 Added SingleSelect component. |
/progress 15 Added the TextInput component. |
/progress 60 |
/progress 90 |
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 ❤️ |
still relevant. |
Add the form component into the design system
Out of scope
As part of this PR you might decide to create other components like "DropDown" for instance
Related to #748
The text was updated successfully, but these errors were encountered: