-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
regression: Do not throw an error when a required custom field is missing on visitor to contact migration #34071
regression: Do not throw an error when a required custom field is missing on visitor to contact migration #34071
Conversation
…sing on visitor to contact migration
Looks like this PR is ready to merge! 🎉 |
|
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-7.1.0 #34071 +/- ##
==============================================
Coverage 75.75% 75.75%
==============================================
Files 510 510
Lines 22078 22078
Branches 5387 5387
==============================================
Hits 16726 16726
Misses 4706 4706
Partials 646 646
Flags with carried forward coverage won't be shown. Click here to find out more. |
…sing on visitor to contact migration (#34071)
Proposed changes (including videos or screenshots)
Introduced here: #32727
Issue(s)
Steps to test or reproduce
Further comments
On visitor to contact migration, we shouldn't throw errors in any of these cases:
#34030 has only partially fixed this issue (the second item has been addressed, but not the first one). In order to not throw errors on visitor to contact migration, we should skip the whole repeated validation process so that missing required fields do not generate an error.
SCI-179