Version 0.5.0 Levenstein updates and fuzzy matching

[fbennett]

• Graceful Levenshtein updating of search list
• Search queries as fuzzy match to each term, joined by AND
• Force query words to lowercase
• Fix an issue with failure of DOM updates on first search
• Update README
• Update changelog.txt

[fbennett]

Hope this checks out okay in trials!

[Windyo]

I'll look at it this weekend, kinda swamped ATM.

Quick question: you changed from .4 to .5 - does that mean you're expecting breaking changes ?

Cheers

[fbennett]

No rush at all. The changes require an id and a specific class attribute on result_template for screen updates to work correctly. It's a small change for theme developers, but if they have defined their own result_template and don't make the adjustment, screen updates will not work correctly.

[fbennett]

I just force-pushed a further small change. Testing locally, we found that search could be broken if user made a search attempt immediately on first access to the site. Running indexing_start immediately when index generation is required helps protect against that glitch. No other impact.

[fbennett]

Fixed a couple of other bugs, including what looks like a change in the way dates are handled in some contexts---the tool worked on our production server with MySQL and Ghost v1.20.0, and failed locally on a v1.20.3 sqlite3 installation. A tweak to normalize the date form for an API call fixed it. Should be pretty solid at this point.

[Windyo]

You're fixing stuff too fast xD I'll look at it this weekend, thanks Sent from BlueMail<http://www.bluemail.me/r?b=11745> On Jan 25, 2018, at 16:09, Frank Bennett <notifications@github.com<mailto:notifications@github.com>> wrote: Fixed a couple of other bugs, including what looks like a change in the way dates are handled in some contexts---the tool worked on our production server with MySQL and Ghost v1.20.0, and failed locally on a v1.20.3 sqlite3 installation. A tweak to normalize the date form for an API call fixed it. Should be pretty solid at this point. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#45 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ARG2-65ZVoESjd2UgxPLgwAExYHRPeANks5tOJkMgaJpZM4Rpfb1>.

[fbennett]

Yeah, it got to be a little obsessive there for a bit. Should be settled now, though. Have a good weekend!

[fbennett]

Rats. Searches are behaving weirdly on first-access with iOS devices. Erratically. Working on it, but not ready for merge yet. More soon ...

[fbennett]

Pretty sure I found the problem. It looks to be a bug in lunr.js specfiic to iOS. I've filed a pull request to lunr.js with my hackity fix, and I'll update this item shortly to use a static copy of the lunr.js module for the nonce. More soon ...

[fbennett]

There we go, the deed is done. We're now getting identical results without crashes on Linux and iOS devices. I've squashed everything into a single commit. I think this does it. 🤞

[fbennett]

Added one more small tweak. The meta_description field does not (yet) return anything for posts. The user's hand-drafted description, if any, comes through in custom_excerpt, so I shifted to that instead for the description value in the index return.

[Windyo]

@fbennett I ahven't forgotten you, I got a bit swamped, sorry. I'll finish testing and put it live by Sunday barring any issues.

[fbennett]

No worries at all. I know swamped.

[Windyo]

thanks :)