Documents check for whether a mobile is taken, and clarifies we won't update an existing number if a different one has been found
Updates a stale test that was throwing an undefined index error -- getUserSmsSubscriptionUpdatePayload was refactored in #172 to only be used when an import row has a mobile (moving the check into handle instead of updateUserIfChanged)
What's this PR do?
Cleanup from #172:
Documents check for whether a mobile is taken, and clarifies we won't update an existing number if a different one has been found
Updates a stale test that was throwing an undefined index error --
getUserSmsSubscriptionUpdatePayloadwas refactored in #172 to only be used when an import row has a mobile (moving the check intohandleinstead ofupdateUserIfChanged)How should this be reviewed?
👀
Any background context you want to provide?
I'm realizing the "Online Drives" section of the docs need a major overhaul per our new OVRD pages, which I plan to tackle in tandem with updating the Voter Registration tracking source docs mentioned over in https://github.com/DoSomething/phoenix-next/pull/2164#discussion_r428714489
Relevant tickets
References Pivotal #172805635.
Checklist