You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"dynamic_forms": [
{
...,
"schema": {
...,
"job_description": {
"type": "array",
"title": "15. Please include a job description for the role if available."
}
},
"options": {
"fields": {
...,
"job_description": {
"type": "upload", <<<
"hideNone": true,
"sort": false
}
},
}
}
]
right now, the configureDynamicFormSchema function assumes that the required and dependencies properties will be present on each schema field. they may not be however. currently, when they are not present, they throw an error. so far I've seen that happen when the type for a property is upload, e.g. options.job_description.type. it may need to be accounted for other types too however.
Acceptance Criteria
radio
checkbox
select
textarea
text
date
upload
Screenshots / Video
Testing Instructions and Sample Files
Notes
The text was updated successfully, but these errors were encountered:
Story
ref: https://assaydepot.slack.com/archives/C03FZDALABG/p1707497250962569
we need to account for the various
types
that are available as a dynamic form option so that the new request form renders properly. e.g.right now, the
configureDynamicFormSchema
function assumes that therequired
anddependencies
properties will be present on each schema field. they may not be however. currently, when they are not present, they throw an error. so far I've seen that happen when the type for a property isupload
, e.g.options.job_description.type
. it may need to be accounted for other types too however.Acceptance Criteria
Screenshots / Video
Testing Instructions and Sample Files
Notes
The text was updated successfully, but these errors were encountered: