Visual Designer: Form component
Add the form component into the design system
The Form component represents a document section containing interactive controls for submitting information
Out of scope
- The ChipInput component
As part of this PR you might decide to create other components like "DropDown" for instance
Related to #748
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. Imma pick this one up. 😄
/progress 10 tested if https://github.com/rjsf-team/react-jsonschema-form is the right fit and it doesn't seem to be the right solution for us for the following reasons:
- it is UI Framework bound which means no tailwind to customise.
- Our schemas for AsyncAPI file and bindings are not fit for this purpose.
- It can't be used in server components.
@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 The PR is ready for review.
/progress 90 The PR is ready for review.
This issue has been automatically marked as stale because it has not had recent activity :sleeping:
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 :heart:
still relevant.