I noticed that if I search for an entry by using the first couple letters of an entry title, that the plugin will search for those letter anywhere in an entry title instead of first checking the first couple letters of the title.
For example, if I have an entry called ebay.com and an entry called agilebits.com and type "eb" into the search bar, agilebits.com comes up as a result because "eb" is in the title name. agilebits.com also comes up as the first result instead of ebay.com
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm. I want to keep the behaviour where it searches anywhere within the entry, not just at the start. It would be nice to prioritise results where the text was found at the start, though. I'll have a go at adding results prioritisation for the next version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've done some experimentation with this. In some cases it can be a bit disconcerting because as the search continues, new results may end up being added above the currently visible results (rather than always at the end), so it makes the results list feel a bit 'jumpier'. On the other hand, the results that jump to the top are almost always more useful, so there's certainly that.
I've attached a preview of v0.3 which prioritises results starting with the search term; I'd appreciate it if you could give it a try for a bit and let me know how it feels in use for you.
I noticed that if I search for an entry by using the first couple letters of an entry title, that the plugin will search for those letter anywhere in an entry title instead of first checking the first couple letters of the title.
For example, if I have an entry called ebay.com and an entry called agilebits.com and type "eb" into the search bar, agilebits.com comes up as a result because "eb" is in the title name. agilebits.com also comes up as the first result instead of ebay.com
Hmm. I want to keep the behaviour where it searches anywhere within the entry, not just at the start. It would be nice to prioritise results where the text was found at the start, though. I'll have a go at adding results prioritisation for the next version.
I've done some experimentation with this. In some cases it can be a bit disconcerting because as the search continues, new results may end up being added above the currently visible results (rather than always at the end), so it makes the results list feel a bit 'jumpier'. On the other hand, the results that jump to the top are almost always more useful, so there's certainly that.
I've attached a preview of v0.3 which prioritises results starting with the search term; I'd appreciate it if you could give it a try for a bit and let me know how it feels in use for you.