orama does not go to the section of the page where the result is

[EscapedGibbon]

For some reason the oramasearch doesn't add to the url #the-section-where-it-found-the-match part and instead of going to the page section, only opens the page where the match was found.

[EscapedGibbon]

This issue requires PR #98 to be merged before working on it.

[EscapedGibbon]

I would like to hear your opinion about this. So, I looked at the orama plugin of docusaurus v2 and when it was building search sections it used to have a property called "hash".

With v3 this property was removed.

But the path property remained. Thus, when I console.logged the sections' paths when they are built, for instance our "Glossary" sections looked like this.

Every section in Glossary has the same path, because the the original title section has this path. Therefore, I assume that we can add an anchor to each section's path by adding the section title to the path string(only if the original title !== section title).
This means that the way orama parses HTML content needs to be changed. The function that does it is here.

https://github.com/askorama/orama/blob/f8b04e90f4319b54662efca573aa4e4edde7096e/packages/plugin-docusaurus-v3/src/index.ts#L199

[EscapedGibbon]

My questions are:

1. Does what I am saying make sense?

2. If yes, should I investigate a bit further and try to fix it at least locally? For example, I am not sure how orama behaves if there several titles in one page which are the same. Or if the title is in not in H1 tags.

3. What is the approach after? This is the orama issue, not image-js-docs. So how will fixing orama issue look like?

[targos]

@stropitek I let you answer.

[stropitek]

We looked at this together and plan is to make a PR in orama which adds the hash to the path.

[stropitek]

https://github.com/askorama/orama/releases/tag/v2.0.23

This release adds the missing feature.

https://github.com/askorama/orama/pull/755/files