'notFound' template not return current user query

[AlonsoK28]

This is usefull to render templates with an improved UX

example

const template = `
          <div class="d-flex align-items-center justify-content-center">
            <span>Not found results founds with your query {{query}}</span>
          </div>`;

More about this into jQuery Typeahead documentation http://www.runningcoder.org/jquerytypeahead/documentation/

[SneakyGerald]

I think it would be useful to have more data in all templates: header, footer and notFound, to give more information to the user for better UX, for example, total results found, manage additional logic to show "see more" button depending on results found, etc...

[niketpathak]

Hello, yes, thank you for your valuable suggestions @AlonsoK28 and @SneakyGerald . This will be coming up soon in the next release. Will update when that happens! Good day

[AlonsoK28]

for me a workaround was like the following:

notFound: () => {
        const query = document.querySelector('#searchInputTypeahead').value;
        const slug = gen(generateSlugSearch(query), slugTypes.search);
        const template = `
          <div class="d-flex flex-column align-items-center justify-content-center">
            <span>Aun no hemos encontrado resultados</span>
            <button class="btn btn-primary my-2" type="submit" onclick="window.location.href = '${slug}'">
                <div class="d-flex align-items-center">
                    <i class="fas fa-search pe-1"></i>
                    Ampliar más la búsqueda
                </div>
            </button>
          </div>
        `;
        return template;
      },

[niketpathak]

Hello @AlonsoK28 , @SneakyGerald , as of v4.16.0, typehead provides additional data within templates. You may refer the docs for implementation details and a live example can be found on the playground

@AlonsoK28,

To access the query within the notFound template, you can simply do

notFound: (resultSet) => {
   return `Nothing found for "${resultSet.query}"`;
}

Besides the query, you can also access additional data like the count (i.e. total suggestions found) and so on.

Hope that helps!