-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Search: Only use generic parsers #10272
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
Comments
Looks good. Not sure if we need to back up the tables, since we aren't using them anymore, but not strong opinion about not doing it. We should also check if we can remove the generation of the
|
💯 , this will speed up the build time a little bit. I'm 👍🏼 on removing it if possible. |
We are indexing sphinx domains as sections now, we no longer need to create sphinx domains or index them. We should see some small improvement in build time, and maybe in search? This change will require a re-index, since old projects that haven't been re-build still have sphinx domain objects indexed separately from sections (this step can be done after or before the deploy). This also fixes a small bug, we are still indexing sphinx domains titles, without their content  ref #10272
It would be awesome to return to this work and finish this project (cc @ericholscher). The work on this issue will allow us to use always the same parser without matter the doctool the user is using (which will give them the exact same search experience). We are pretty close now! I arrived here while doing the cleanup of the feature flags at #9779 Remember to remove the |
Agreed, this is a useful next step on this work. I thought we'd already finished making everything use the HTML-only parsing. |
While reviewing #10042 I found the work from this issue is, in part, required to removed the |
We're slowly rolling this out via feature flag 👍 |
We were using these for search, but we no longer need them. We index the HTML directly now. Ref readthedocs/readthedocs.org#10272
Closes #10272. We can't remove the code that generates the fjson files, since they are being used by the embed API (v2), that API is mentioned as deprecated, we should do the actual deprecation by contacting projects using it.
Closes #10272. We can't remove the code that generates the fjson files, since they are being used by the embed API (v2), that API is mentioned as deprecated, we should do the actual deprecation by contacting projects using it. --------- Co-authored-by: Manuel Kaufmann <[email protected]>
Since #10128 removed specific Sphinx domain logic in the
SphinxParser
, we aren't doing much more search indexing that's specific for Sphinx or MkDocs.SphinxParser
redundant (move anything essential into theGenericParser
)MkDocsParser
redundant (move anything essential into theGenericParser
)readthedocs.sphinx_domains
application?CC: @stsewd does this list look good? Perhaps we can break into separate issues/PRs if any change becomes too complex.
The text was updated successfully, but these errors were encountered: