Love this. Very clear to the user that a question is required or value is outside the constraint.
I'm more likely to use custom required_message values for questions now with this change.
I tested a four level cascading select and changing higher levels caused the lower ones to update to the correct filtered choices.
This is fantastic! I had just been living with this as I have a lot of name values with multiple underscores and when I show them (instead of pulling the choice-name) the display was always a little skewiff
Maintain last-saved across definition updates
This is worth noting for those that use it either as previously implemented or doing funny things to build strings between updates. I'll have to adjust a few forms as they will now not reset the value post update and will end up massively long.
@TobiasMcNulty this was a change you were after?