lukewhitehouse/gatsby-starter-blog-with-lunr

Building upon Gatsby's blog starter with a Lunr.js powered Site Search. https://gatsby-starter-blog-with-lunr.netlify.com/

gatsby-starter-blog-with-lunr's Issues

Some feedback

I know you didn't ask for it but I'll write it anyway because I like your posts.

• If you press : in the search you get this error:

O.QueryParseError {name: "QueryParseError", message: "unrecognised field '', possible fields: 'title', 'description', 'content', 'url', 'date'"....

• Word highlighting would be nice. For example:

<p>
  <Highlighter
     searchWords={[query]}
     autoEscape={true}
     textToHighlight={description}
    />
</p>     

• Clear the results when the input is cleared. Maybe something like this in the useEffect of search.js:

if (!searchQuery) setResults([])

useEffect has a missing dependancy

Hi,

Great search utility - thank you for sharing!

I have implemented your code but am getting the following message in the terminal:

warn ESLintError:
C:\home\lunr-search\src\pages\search.js
25:6 warning React Hook useEffect has a missing dependency: 'searchQuery'. Either include it or remove the dependency array react-hooks/exhaustive-deps

✖ 1 problem (0 errors, 1 warning)
0 errors and 1 warning potentially fixable with the --fix option.

I'm completely new to React and Gatsby, so this has stumpped me somewhat! Any help gratefully received.

Many thanks

URLSearchParams is not defined

When doing a gatsby build, I get a failure due to the following reason:
URLSearchParams is not defined.

Search on onkeyup?

Am reading your tutorial https://assortment.io/posts/gatsby-site-search-lunr-js where you ask for feedback. Hope here is OK. The tutorial is excellent. I have made a version of the blog with more text and frontmatter to check out functionality.

I noticed that mostly you have to type a full word in the search box before results are triggered. Just a few exceptions showed results before, eg entering "sweep" showed a record with "sweeping", and "privat" showed record with "private". But you must enter the entire word to get a record with "peninsula". Is there any way to trigger search after each onkeyup instead?

Subject to the above, the Submit button seems unnecessary as results appear when typing in the search term.

One last finding on search: once the search is triggered and results appear, if you carry on typing these results do not change. This is not desirable. For example one record has "look no further", another has "looking". Both appear after entering "look" but stay there after extending the search to "look further". Is there an easy solution?