Use URI instead of path for read more keyword read more links

[vinistock]

Motivation

I noticed that the read more links weren't working. The reason is because Markdown links always need to use URIs and not file paths.

Implementation

Corrected the links to use URIs.

Automated Tests

Updated the tests, which were asserting the wrong behaviour.

[vinistock]

• Use URI instead of path for read more keyword read more links #3873 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label graphite-merge to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[st0012]

If we use yield as an example, there should we take user for the doc?
I'm on v0.26.4 and clicking the read more for yield opens /Users/hung-wulo/.gem/ruby/3.4.0/gems/ruby-lsp-0.26.4/static_docs/yield.md in my editor. Is this the expected behaviour?

[vinistock]

I'm on v0.26.4 and clicking the read more for yield opens /Users/hung-wulo/.gem/ruby/3.4.0/gems/ruby-lsp-0.26.4/static_docs/yield.md in my editor. Is this the expected behaviour?

Yup. We ship the static docs as part of the gem so that we can open expanded documentation directly in the editor.

Without this fix, the link doesn't even render because the editor expects URIs and not file paths.

[st0012]

But it does render for me 🤔
I'm not on this branch. I'm using the v0.26.4 release in the RDoc codebase

[vinistock]

Oh, weird. I'm not sure why I can't see the links if they are not URIs. Do you still see them on this branch?