Open pcantrell opened 1 year ago
I'm running into the same issue. Is it worth displaying an email address as well to differentiate between records?
We managed to manually right the presentations last night.
To compound the issue, the Twitter autocomplete library, rest in peace, is no longer around and appears to not handle id
and name
pairs.
The selected name is passed to Rails, and it then does another lookup which AFAIK will result in always the first "John Doe" match, but not necessarily the one that was selected. I suspect it's going to be the one with the lowest ID.
First, replace the library with a more correct library where we can pass the selected ID (user's intent).
I'll be putting up a PR to address the issue.
refs #304
/cc @experimatt
I share your hesitation to display users' email addresses, but I do like the idea of being able to find a user by inputting their email address. This definitely feels like an edge case (that's going to keep popping up) until we 1) address duplicates in the database, and/or 2) work in a better longer term solution.
I provided a report to the team with duplicates so we can manage it better short-term.
PR #305 addresses a more fundamental issue where even if there 2 or more people who show up in the user interface, the same one will always be looked up by the database.
Agreed on finding by email. It will take more work since the endpoint is not a search endpoint, but an in-browser search of the participant universe. We cannot expose emails there as a UX patch without doing it correctly...too public.