-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[issue]: lunr-search doesn't pickup on heading elements that are non-direct children of '.markdown' #115
Comments
Hello @praveenn77 , any chance you could have a quick look here? I'd be willing to work on a PR if you're too busy, but it would be great to get some insights from you first. Thanks |
Hi @Jeandcc , thanks for reporting this issue, Hope this helps, |
Hi @praveenn77 , thanks a lot for the code you built for this functionality! I took the freedom to further develop this feature, aiming at reducing the workload for developers in case they have headings on different levels of hierarchy. With the previous approach, devs would have to add the With the PR #117 that I opened, this would not be necessary, as the code would look through all direct and indirect children of the element with the Could you please take a look at it, and let me know in case of questions or requests for tweaks? Thanks! |
Here's a demo codebase used to replicate the issue: https://github.com/Jeandcc/wrapped-heading-issue-w-docusaurus-lunr-search
As you can see on this file, we swizzled the
DocItem
'component' so we can render some content on the documentation page based on the Front Matter data as well, and not only on the markdown of the page.Here's the example doc used to render Front Matter content as well as MD content.
The problem that we are currently facing is that
docusaurus-lunr-search
only pickups the heading elements that are direct children of the.markdown
element. Headings that are encapsulated by other elements, such asdivs
, will not get picked up for indexing bylunr-search
.Here's "visual proof":
Visual preview of the documentation page
Searching for top-level heading generated with FrontMatter and Swizzling:
Searching for non-top-level heading generated with FrontMatter and Swizzling:
After browsing the
docusaurus-lunr-search
codebase, I believe the fix for this issue will touch on these lines of the codebase:docusaurus-lunr-search/src/html-to-doc.js
Lines 109 to 118 in 44be1f0
The text was updated successfully, but these errors were encountered: