display search result with a tree #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
It's a bit tricky but I think I solved the issue I mentioned
|
Florent-Bouisset
force-pushed
the
feat/search-result-indented
branch
from
1432007 to
f9aa2ea
Compare
Florent-Bouisset
force-pushed
the
feat/search-result-indented
branch
2 times, most recently
from
7559523 to
dbd7f32
Compare
Florent-Bouisset
force-pushed
the
feat/search-result-indented
branch
from
dbd7f32 to
7a6df87
Compare
peaBerberian
reviewed
Jan 8, 2025
peaBerberian
reviewed
Jan 8, 2025
peaBerberian
reviewed
Jan 8, 2025
peaBerberian
reviewed
Jan 8, 2025
peaBerberian
reviewed
Jan 8, 2025
peaBerberian
reviewed
Jan 8, 2025
peaBerberian
reviewed
Jan 8, 2025
peaBerberian
reviewed
Jan 8, 2025
peaBerberian
reviewed
Jan 8, 2025
peaBerberian
reviewed
Jan 8, 2025
peaBerberian
reviewed
Jan 9, 2025
Collaborator
|
I guess LGTM now :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea of this proposal is to display results with a tree when searching on the doc.
There is an issue if the search result include a subsection but not the parent section, in this case the subsection is orphan, I'm not sure how to handle that.