Skip to content

Search Improvements#878

Draft
wordsandnumbers wants to merge 1 commit intoParkingReformNetwork:mainfrom
wordsandnumbers:865-search-improvements
Draft

Search Improvements#878
wordsandnumbers wants to merge 1 commit intoParkingReformNetwork:mainfrom
wordsandnumbers:865-search-improvements

Conversation

@wordsandnumbers
Copy link
Collaborator

@wordsandnumbers wordsandnumbers commented Jan 27, 2026

TODO

  • Add Tests

Fixes #865

@wordsandnumbers wordsandnumbers changed the title Search on label only and show 10 results instead of 4 Search Improvements Jan 27, 2026
@wordsandnumbers wordsandnumbers force-pushed the 865-search-improvements branch from 1cad517 to cfc746b Compare January 27, 2026 02:53
"customProperties.country",
],
searchResultLimit: 10,
searchFields: ["label"],
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems to work just fine by matching on the label only. 🤷 I added 10 results which addresses the issues in #865

@Eric-Arellano
Copy link
Contributor

Thanks for working on this 🙌 I may take a few days to review because I leave for a one month sabbatical on Friday so am rushing around to finish things.

Regarding the customProperties, this was very intentional so that you can search, for example, "California" and it will look up places that have the state California. See #801. Otherwise, Choices.js uses prefix-matching, so wouldn't match California because the total phrase does not start with California.

I have not closely looked into Tony's frustrations in #865, so I can't give a particular recommendation for how to fix it. But ideally we could preserve the benefits of #801 while addressing Tony's feedback.

@wordsandnumbers
Copy link
Collaborator Author

Thanks for working on this 🙌 I may take a few days to review because I leave for a one month sabbatical on Friday so am rushing around to finish things.

Regarding the customProperties, this was very intentional so that you can search, for example, "California" and it will look up places that have the state California. See #801. Otherwise, Choices.js uses prefix-matching, so wouldn't match California because the total phrase does not start with California.

I have not closely looked into Tony's frustrations in #865, so I can't give a particular recommendation for how to fix it. But ideally we could preserve the benefits of #801 while addressing Tony's feedback.

@Eric-Arellano: Obviously not a rush! Also: Hi! 👋 Nice to meet you via github PR 😆 !
I figured there was a reason you added the customProperties but it wasn't clear what the expectations were. I'll work on a test so we can make sure it meets them.

Have fun on sabbatical!

@wordsandnumbers wordsandnumbers marked this pull request as draft January 27, 2026 21:41
@wordsandnumbers wordsandnumbers force-pushed the 865-search-improvements branch from cfc746b to 0736e9f Compare January 28, 2026 02:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Search is not working as expected

2 participants