-
Notifications
You must be signed in to change notification settings - Fork 12
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
Multi-Word last name or first name #128
Comments
Is this in reference to the app permissions lookup? |
Yes. |
Ok I need a bit more info. Can we assume that if there is a 3rd element then it's First, Middle, and Last name?
Or is there some sort of double last name edge case we're dealing with? |
It is a double last name case. For example: "Joseph Van Boxtel" should split to (First: "Joseph" Last: "Van Boxtel") The following seems to work. |
That is perfect! I'll test it! Or a pull request would be great |
The only think I can think of is that right now we have check_name who's job is to verify they have at least a first and last name, and explain this needs to match Planning Center for the authentication to work. It's now obvious it doesn't quite work. What's your thoughts on this? I think it's pretty messy how I have it currently implemented. |
It seems like this change would make Also, it seems the |
Really good points. I agree check name won't be needed anymore. get_apps will need to be updated too. |
After testing |
We could only do it conditionally if the full name has more than 2 components. |
It was so slow It feels like it Isn’t working at all. User will probably keep resubmitting the request 🤔 |
A slack name with more than two words will not match to the user in Planning Center. This seems to be due to a split on spaces where element 0 is treated as the first name and element 1 is treated as the last name.
The text was updated successfully, but these errors were encountered: