cr-connect-workflow

Author	SHA1	Message	Date
mike cullerton	f883eb2bbe	We now include field.id in the ApiError message for hidden and default validation. (The field must have a default value or value expression) While working on this ticket I found a logic error in the test. I expected both default_value and value_expression. It turns out the default_value is always there, it's just null if we don't set it. Modified the existing test for hidden and required, and added tests to make sure my passing logic is now correct.	2021-03-04 10:42:13 -05:00
mike cullerton	eb504465f6	Test and workflow for new code. We test 2 things. - If a field can be hidden and required, it must have a default value or value_expression - If a field is hidden and required, make sure we use the default value	2021-02-08 10:20:05 -05:00

Author

SHA1

Message

Date

mike cullerton

f883eb2bbe

We now include field.id in the ApiError message for hidden and default validation. (The field must have a default value or value expression)

While working on this ticket I found a logic error in the test. I expected both default_value and value_expression. It turns out the default_value is always there, it's just null if we don't set it.

Modified the existing test for hidden and required, and added tests to make sure my passing logic is now correct.

2021-03-04 10:42:13 -05:00

mike cullerton

eb504465f6

Test and workflow for new code.

We test 2 things.
 - If a field can be hidden and required, it must have a default value or value_expression
 - If a field is hidden and required, make sure we use the default value

2021-02-08 10:20:05 -05:00

2 Commits