Fix nok_first prefill to use nextOfKin.firstName in Register.tsx - #924
Merged
Conversation
ignatiusm
approved these changes
Aug 5, 2026
ignatiusm
left a comment
ignatiusm
left a comment
Contributor
There was a problem hiding this comment.
I didn't test this locally, but the one-word change looks good to me. Nice catch! Approved 🚀
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #923.
One-word fix on line 113 of
application/user-client/src/pages/Register.tsx.nok_first(next-of-kin First Name field) was being prefilled fromnextOfKin?.lastName. Changed tonextOfKin?.firstName.Since the fix is at the rendering layer, it uniformly covers every upstream prefill path (CSV import wizard, direct API, RedCap integration).