Stub in an idea that gets R dev help to refresh #8087
Draft
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.
@softwarenerd I think I'm going to need some help from you on this one. I don't anticipate this being merged as is, but I wanted to get some of your thoughts on it now
When writing development documentation for R packages, you typically are in a hot iterative loop of:
devtools::document()
?function_name
devtools::document()
?function_name
(here's where a problem lies)This doesn't currently work with our help server. It pseudo-caches the help url we were previously on, so if you navigate to the same url twice in a row, no refresh occurs. I'm not sure this is right, because I don't think the frontend can really "know" if the url's content is static (much of the time it is) or dynamic (like with dev help in this example) and has changed out from under it.
You currently have to navigate to a completely different page, and then recall
?function_name
, and then it will refresh.Here is what it currently looks like:
Screen.Recording.2025-06-12.at.11.54.41.AM.mov
Here is what I am expecting it to look like (with this PR idea):
Screen.Recording.2025-06-12.at.11.51.53.AM.mov
This patch doesn't fully fix all of the problems. There are some issues with the left arrow "navigate backwards" command (shown in the video below), for example:
?function_name
?abs
devtools::document()
function_name
pageIf you do this, we still don't get a refresh. I don't find any evidence that our proxy is even getting a "request" to render this content, so it is possible this issue is deep in the proxy server rather than at the help service level, but I am not sure.
Screen.Recording.2025-06-12.at.11.55.41.AM.mov