SF-3664 Fix projects creating duplicate Paratext User entries #3634
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.
This issue happens when a user began as a Username-Password user that was later linked to a Paratext identity. When a user joins a project, if the user happens to have an alternate username on the user doc different than in Auth0, then a duplicate paratext user entry will be added to the ParatextUsers collection on the project. Some projects on QA, and on 1 project on live experienced this. The only issue this poses is that multiple users may appear in the users list.
This change ensures that we use the paratext username as the key to determine if a new entry should be inserted into the ParatextUsers collection on a project.
Cleaning up the QA and live projects will be a separate task.
This change is