Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Better component mapping #5

Open
drazik opened this issue Apr 18, 2023 · 0 comments
Open

Better component mapping #5

drazik opened this issue Apr 18, 2023 · 0 comments

Comments

@drazik
Copy link
Contributor

drazik commented Apr 18, 2023

Currently we map components by widget. It may be better to split it by two levels:

  1. type: string, boolean, object, array...
  2. then widget

It would allow more generic typing at the library level (only for type), then each consumer can have the subtypes it needs. For example a specific widget for { type: "string", widget: "password" }.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@drazik