-
-
Notifications
You must be signed in to change notification settings - Fork 828
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
DedupeFind: Treat zip search input strings as prefix #8464
DedupeFind: Treat zip search input strings as prefix #8464
Conversation
… strings as prefix
@yurg would you be interested in reviewing this PR? |
@JoeMurray |
Thanks again for your help. Sure I'll try to guide you. Check out the Review Tips and FAQ tabs as well as Overview of https://docs.google.com/spreadsheets/d/1fmHFOZ83ectSPCMWvXwCeJgrw4KpYi8JEV2ZDkd6XDU/edit#gid=616660117. Then ask questions in dev channel of https://chat.civicrm.org. |
Actually this is dependent on the other PR I'm looking at - but @yurg we can review them both together. This is the other PR So, the questions we need to answer as reviewers are
|
@eileenmcnaughton just FYI I cribbed your response and worked it into the Reviewer Tips tab. Thanks!! |
yeah - we need to put up a blog - I had hoped one of the sprinters would - not sure if there is some doco that they DID record |
OK an update on this - in the process of fixing https://issues.civicrm.org/jira/browse/CRM-18577 I have done the much -overdue re-write of the function this relies on change to. So, I guess I will have to recut this. @yurg if you feel up for reviewing a different PR you could try this one #8266 - it's fairly simple - just a case of making sure my logic is good |
closing per discussion on #8463 |
When filtering by postal code it's more intuitive to treat the search input as a prefix, i.e. like a startsWith request.
See CRM-18694
Depends on PR #8463