We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have various field types in keeep:
enum AttributeType { TEXT NUMBER DATE CHECKBOX SELECT MULTISELECT URL EMAIL PHONE TAGS FILE SOCIAL @@schema("public") }
While some of them are simple, some others hold a config JSON object that contains information on valid configurations.
config
For example, a select field might store the available options as config:
{ system: false, required: false, label: 'Status', type: 'SELECT', config: { options: [ { label: 'New', value: 'new', color: 'gray', }, { label: 'Contacted', value: 'contacted', color: 'blue', }, ], },
We need to handle this properly in the backend and frontend. How? TBD
The text was updated successfully, but these errors were encountered:
marvin-splitt
No branches or pull requests
We have various field types in keeep:
While some of them are simple, some others hold a
config
JSON object that contains information on valid configurations.For example, a select field might store the available options as config:
We need to handle this properly in the backend and frontend. How? TBD
The text was updated successfully, but these errors were encountered: