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
The search feature should match the branch that the docs loaded in. Why? The use case I often have is I use the search bar to quickly navigate to the page I had just edited in my PR to see how it'd render in prod. The new search engine produces results that always directs to stable, though, so there's no easy way to navigate to the page I wanted to check. This is a regression from the previous search experience.
For example, in the following preview, I'm looking for the custom operators page, which I had modified in the PR. I search for it in the preview docs, but all the results point to stable. Ideally, these would point to the docs built for my PR branch, which was the old behavior.
It would also be good for those look at docs on main to stay in docs on main (vs be redirected to stable).
Alternatives
Allow the old search engine
The text was updated successfully, but these errors were encountered:
The search feature should match the branch that the docs loaded in. Why? The use case I often have is I use the search bar to quickly navigate to the page I had just edited in my PR to see how it'd render in prod. The new search engine produces results that always directs to stable, though, so there's no easy way to navigate to the page I wanted to check. This is a regression from the previous search experience.
For example, in the following preview, I'm looking for the custom operators page, which I had modified in the PR. I search for it in the preview docs, but all the results point to stable. Ideally, these would point to the docs built for my PR branch, which was the old behavior.
It would also be good for those look at docs on main to stay in docs on main (vs be redirected to stable).
Alternatives
Allow the old search engine
The text was updated successfully, but these errors were encountered: