-
Notifications
You must be signed in to change notification settings - Fork 6
54 add widget type field and break the current widget into smaller components #60
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
54 add widget type field and break the current widget into smaller components #60
Conversation
|
Ready to be reviewed |
| "required" : true | ||
| } | ||
| ] | ||
| } No newline at end of file |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's not test this for now. This needs to work with an interactive map widget
max-zilla
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Read through the changes and tested on a fresh database by adding the definitions in data/metadata (except coordinates) and going through each one in a new dataset adding+editing, it all looked good.
|
resolved small merge conflict on .gitignore |
…nt-widget-into-smaller-components
…nt-widget-into-smaller-components


Post definition with supported field widget name will now automatically populate the frontend to construct such form.
Supported widgetType includes
Select,TextField,DateTimePicker. If not supported widgetType was provided, the frontend fallback isTextFielde.g.
More examples see
backend/data/metadata/definitionsfolder