While we've added quite extensive API docs to the SDK (at least to sentry-ruby), it's not easy to find them, which could contribute to misuses/confusion of APIs. Therefore, I think we should make the documentation more discoverable by linking them in the gems table.
And because the table already takes quite big of a space, I decided to remove the downloads column to make room for API doc links. I'm also ok with replacing the coverage column instead though.
For this initial improvement, I chose to use rubydoc.info as the source as it automatically fetches the gems' source and generate the content. I think ideally we can host them with GH pages with a automatic publishing workflow, which will give us more control (example: Ruby LSP). I think this is what sentry-rust does as well?
While we've added quite extensive API docs to the SDK (at least to
sentry-ruby
), it's not easy to find them, which could contribute to misuses/confusion of APIs. Therefore, I think we should make the documentation more discoverable by linking them in the gems table.And because the table already takes quite big of a space, I decided to remove the
downloads
column to make room for API doc links. I'm also ok with replacing thecoverage
column instead though.For this initial improvement, I chose to use
rubydoc.info
as the source as it automatically fetches the gems' source and generate the content. I think ideally we can host them with GH pages with a automatic publishing workflow, which will give us more control (example: Ruby LSP). I think this is whatsentry-rust
does as well?skip-changelog