You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are still generating fjson files for sphinx builds (readthedocs/readthedocs-sphinx-ext#126), at first I thought they were used by our search only, but they are actually being used by th embed API V2 as well. If we fully deprecate/remove the embed API V2, we can delete all the code related to fjson files (generating then and storing them in storage).
I took a look at NR and I found we have just a few projects hitting this endpoint in the last 90 days: https://onenr.io/0PwJEXYO7Q7. We have 28 projects hitting this API and it's mainly because they are using an older version of sphinx-hoverxref
The change from Embed v2 to v3 was done in readthedocs/sphinx-hoverxref#146 and it was released on 0.8b1 and we are on 1.3.0 now.
The good news here is should be easy for these projects to just update this dependency to solve the issue.
I agree with the plan here: deprecate, contact users, wait a month or so, and remove the endpoint.
Once we migrate all users away from using our Sphinx extension, fjson files won't be generated for anyone. People will need to upgrade their version of the hoverxref Sphinx extension to fix this.
Old versions of docs will break hoverxref, but that's probably fine for old versions. New versions can use the new sphinx extension and they will work?
What's the problem this feature will solve?
We are still generating fjson files for sphinx builds (readthedocs/readthedocs-sphinx-ext#126), at first I thought they were used by our search only, but they are actually being used by th embed API V2 as well. If we fully deprecate/remove the embed API V2, we can delete all the code related to fjson files (generating then and storing them in storage).
readthedocs.org/readthedocs/embed/views.py
Lines 192 to 202 in 40bfe63
Describe the solution you'd like
Fully deprecate that endpoint, similar to the recent deprecations we have been doing, maybe contact the projects that are using it.
Alternative solutions
Additional context
The text was updated successfully, but these errors were encountered: