-
Notifications
You must be signed in to change notification settings - Fork 42
Fix: Record Merging “Auto-populate” preference applies in reverse #7478
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
base: main
Are you sure you want to change the base?
Conversation
emenslin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Verify that enabling the Auto-populate preference pre-fills merge fields, while disabling it leaves them blank.
I noticed that for some fields they are not auto-populated when they should be or they are auto-populated when they shouldn't be. I'm not sure why this is or if this is intentional but I've been able to recreate it with a few different fields.
With auto-populate on the date of birth and death precision are not populated:

… enabled and leaves them blank when disabled
Triggered by ba1cb77 on branch refs/heads/issue-4869
emenslin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.



Fixes #4869
The record merging dialog was using the auto-populate preference in reverse—fields were prefilled when the preference was disabled and left blank when enabled. The boolean check has been corrected so that enabling the preference now correctly triggers field auto-population.
Checklist
self-explanatory (or properly documented)
Testing instructions