Add Rubydex linter Ruby LSP addon - #987
Open
st0012 wants to merge 1 commit into
Open
Conversation
st0012
force-pushed
the
codex/linter-explain-command
branch
from
August 6, 2026 17:17
5524cc9 to
f5d2a4c
Compare
st0012
force-pushed
the
codex/linter-ruby-lsp-integration
branch
from
August 6, 2026 17:17
cf7903a to
90fed04
Compare
st0012
force-pushed
the
codex/linter-explain-command
branch
from
August 6, 2026 18:32
f5d2a4c to
1e1bd9c
Compare
st0012
force-pushed
the
codex/linter-ruby-lsp-integration
branch
from
August 6, 2026 18:32
90fed04 to
5f23055
Compare
st0012
force-pushed
the
codex/linter-explain-command
branch
from
August 6, 2026 19:30
1e1bd9c to
e52a7ef
Compare
st0012
force-pushed
the
codex/linter-ruby-lsp-integration
branch
from
August 6, 2026 19:30
5f23055 to
24921d7
Compare
st0012
force-pushed
the
codex/linter-explain-command
branch
from
August 6, 2026 20:33
e52a7ef to
f2fcd8a
Compare
st0012
force-pushed
the
codex/linter-ruby-lsp-integration
branch
2 times, most recently
from
August 6, 2026 21:06
4bc5773 to
1c7f1e7
Compare
st0012
force-pushed
the
codex/linter-explain-command
branch
from
August 6, 2026 21:06
f2fcd8a to
59c5d99
Compare
st0012
force-pushed
the
codex/linter-ruby-lsp-integration
branch
from
August 7, 2026 17:11
1c7f1e7 to
c210581
Compare
st0012
force-pushed
the
codex/linter-explain-command
branch
from
August 7, 2026 17:11
59c5d99 to
38b16d7
Compare
st0012
changed the base branch from
codex/linter-explain-command
to
codex/linter-rule-authoring
August 7, 2026 17:11
st0012
force-pushed
the
codex/linter-rule-authoring
branch
2 times, most recently
from
August 7, 2026 20:16
ed23857 to
0a7b9e1
Compare
st0012
force-pushed
the
codex/linter-ruby-lsp-integration
branch
from
August 7, 2026 20:21
c210581 to
12adbe4
Compare
st0012
force-pushed
the
codex/linter-ruby-lsp-integration
branch
from
August 7, 2026 22:00
12adbe4 to
b1a3c36
Compare
st0012
commented
Aug 7, 2026
|
|
||
| #: (Graph, rules: Array[singleton(Rule)], config: LinterConfig) -> void | ||
| def initialize(graph, rules:, config:) | ||
| raise ArgumentError, "At least one linter rule is required" if rules.empty? |
Member
Author
There was a problem hiding this comment.
We need to stop raising this or the addon would raise in projects don't have rules.
st0012
commented
Aug 7, 2026
| module Linter | ||
| module RubyLsp | ||
| class Addon < ::RubyLsp::Addon | ||
| CONFIGURATION_FILE = "rubydex.toml" #: String |
Member
Author
There was a problem hiding this comment.
This name is declared in Rust so we don't have a way to avoid this here.
st0012
marked this pull request as ready for review
August 7, 2026 22:19
st0012
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add an optional Ruby LSP add-on that runs discovered Rubydex linter rules after saved workspace changes and publishes severity and related information with each diagnostic. It reuses the workspace graph, clears stale diagnostics, and treats workspaces without rules as a no-op.