fix: List should record val
, not text
, in passport and calculate total units by development type when applicable
#3263
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why:
development
typeonSubmit
for any schemas that set a field withfn = development
for nowval
of the selected option if set, rather than itstext
val
will also be useful later when populating the ODP Schema, as it fits our current pattern of looking up a description from value rather than the other way aroundtext
, even if aval
is recorded in the passportChanges
val
where expectedval || text
(val is optional & text is required)