Algolia search does not find code in code blocks?

[slorber]

🐛 Bug Report

Search for beforeDefaultRemarkPlugins

This term exist here in a code block: https://v2.docusaurus.io/docs/using-plugins/#docusaurusplugin-content-blog

[slorber]

@francoischalifour any idea?

[anshulrgoyal]

the code block is not scrapped by default

[anshulrgoyal]

u need to add it scrap config

[s-pace]

👋 @slorber and @anshulrgoyal,

I am part of the DocSearch team.

Usually we do not recommend indexing code samples. These samples are often very similar and duplicated along your documentation such as examples. It introduces noise to the user experience. Displaying matching code would require to enlarge the snippeting to give the context of the matching token.
There is also room for improvement in the way we handle special characters such as dot and dash that can’t be interpreted as separators yet. This is an improvement that we’re investigating on.

[anshulrgoyal]

Hi @s-pace,
I am trying to build an offline search feature for docusaurus. Here is the PR #3153 and https://deploy-preview-3153--docusaurus-2.netlify.app are deployed link. It would be great if u can give some feedback.

[slorber]

Hi @s-pace

Wonder if you have an idea to index correctly API items that are only found in code-block? Do we rather document everything outside of code blocks too?

[s-pace]

I would definitely recommend to document all API items outside of code-block. It enables a better UX to redirect end users with scrolling to the exact matching item. It also helps to give the context of the matching item when the search query is matching the description of the API item. Last but not least, the relevancy would be better since matching a lvl3 / <h3/> element has a stronger impact on the ranking formula.

[slorber]

Thanks

Closing this, but we'll need to document better some attributes that are only found in code blocks

[s-pace]

👋 @slorber
Just a follow up that thanks to algolia/docsearch-configs@cfc5738 we are now indexing CLI options such as --skip-build

[slorber]

thanks

wonder what you can do for the original usecase I had ^^ (beforeDefaultRemarkPlugins)

[s-pace]

👋 @slorber

beforeDefaultRemarkPlugins is too much present within the page. Elements matching [class^='codeBlockContent_'] selector are too similar and it degrades the search experience. Last but not least, we recommend that selectors match small piece of text to enhance the relevancy. These code blocks are too long.