-
Notifications
You must be signed in to change notification settings - Fork 38
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
Enable / Disable Custom Value Input #147
Comments
Any question where there's just a small set of accepted answers; there's
|
Another would be |
honestly I think 90% of the time we do not want the user to be able to enter a custom value. For me the default should be tags/option only with flag for the potential 'other' value similar to how ODK works now. |
Ok, I'll have it off by default. |
In the constraints JSON, the custom value input will be enabled if: "shop": {
"custom_value": true
} where |
Sometimes we might not want to allow a custom value input for the user.
One example is could be
building
. When this feature was requested, what tags did you have in mind?cc/ @PaulUithol @dalekunce
The text was updated successfully, but these errors were encountered: