Closed MarcMichalsky closed 4 months ago
I'm pretty sure @bjendres would like this to depend on a configuration option for the matcher plugin with a default fallback to the current behavior in case someone relies on it.
Well, we could of course just add another mode.
I'm pretty sure @bjendres would like this to depend on a configuration option for the matcher plugin with a default fallback to the current behavior in case someone relies on it.
I don't think that's necessary, since @MarcMichalsky introduced a new name_mode
called db2
.
I don't think that's necessary, since @MarcMichalsky introduced a new
name_mode
calleddb2
.
Yep, after I raised that concern … well, actually still your concern I guess ;-)
@MarcMichalsky thanks, that was quick!
Yes, I did that because of @jensschuppe's comment.
Sometimes I lack the perspective of a service provider who serves many customers. I usually only look at problems like this from our perspective. 🙈
As soon as I have time, I'll be happy to write a test for this.
As soon as I have time, I'll be happy to write a test for this.
We'll wait for that, then. But if it becomes clear you won't be able to in the near future, give us a shout.
Added more logic to cover the common case of <lastname>, <firstname>
pattern.
Merged, thanks!
Let's add docs for those CiviBanking plugins, I created #114 as a follow-up.
This commit improves the name extraction for the db mode.
Comparison of the results
Original function
Modified function