-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
Fix #325 - Required validation #326
base: hotfix
Are you sure you want to change the base?
Fix #325 - Required validation #326
Conversation
Hi @yunusyerli1, I think has already been fixed. Do you confirm? |
Yes, ı do confirm but there are repetitive lines. |
Hey @yunusyerli1 ! It looks like your "How to Test this" sections contains instructions that refer to an already customized instance, so I'm not 100% sure how to confirm the initial issue or proposed fix. Is this just validation for Dynamic Dropdowns, or dependant fields? Could you add some more generic replication/testing steps, that would be more for a vanilla Suite8 environment? Thanks! |
This is for dynamic dependants of a dropdown validation. It was customized instance with new module with some different services. |
Hey! hmmmm, in that case, do you see this having any possible issues worth testing for, @clemente-raposo ? Thanks! |
Description
Just changed order of below lines: #325
data.field.definition.required = required;
data.field.formControl.setValidators(validators);
data.field.formControl.updateValueAndValidity({onlySelf: true, emitEvent: true});
record.formGroup.updateValueAndValidity({onlySelf: true, emitEvent: true});
Motivation and Context
How To Test This
Choose Service as Missed Collection in Case Module.
Select Yes in Further Action Required field.
Fill Outcome field.
Click Save and Continue button.
Check Outcome field again.
Types of changes
Final checklist