lint_roller 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +7 -0
- data/.standard.yml +3 -0
- data/CHANGELOG.md +5 -0
- data/Gemfile +9 -0
- data/Gemfile.lock +57 -0
- data/LICENSE.txt +21 -0
- data/README.md +176 -0
- data/Rakefile +12 -0
- data/lib/lint_roller/about.rb +9 -0
- data/lib/lint_roller/context.rb +11 -0
- data/lib/lint_roller/error.rb +4 -0
- data/lib/lint_roller/plugin.rb +22 -0
- data/lib/lint_roller/rules.rb +17 -0
- data/lib/lint_roller/version.rb +3 -0
- data/lib/lint_roller.rb +11 -0
- metadata +60 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: 247433b599df47c6817d7afaafd5da089706ebcae854383d12e96c6c9551113a
|
4
|
+
data.tar.gz: 1f6d77951ed64e2f52d5145fed81b8eb0d5ad1befa353e20b3ce65c33d233e50
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: d826ec3722b1d85f1f718519ea5958e89dc22878f02e9e6f3b4d601a2a1e8d159be91a0c4f7dc1de0fb5245add220d4d656f6547b6d24f33d6dc84ae77347e09
|
7
|
+
data.tar.gz: d86e1f61d4eb7702014e5509d83a424fa74fb20efcb0209f775213313db90ee4e5cf2446a58038b002efd6532bcc9059fd72cb03dc7ef96f11b84bcc28f2b257
|
data/.standard.yml
ADDED
data/CHANGELOG.md
ADDED
data/Gemfile
ADDED
data/Gemfile.lock
ADDED
@@ -0,0 +1,57 @@
|
|
1
|
+
PATH
|
2
|
+
remote: .
|
3
|
+
specs:
|
4
|
+
lint_roller (1.0.0)
|
5
|
+
|
6
|
+
GEM
|
7
|
+
remote: https://rubygems.org/
|
8
|
+
specs:
|
9
|
+
ast (2.4.2)
|
10
|
+
json (2.6.3)
|
11
|
+
language_server-protocol (3.17.0.3)
|
12
|
+
m (1.6.1)
|
13
|
+
method_source (>= 0.6.7)
|
14
|
+
rake (>= 0.9.2.2)
|
15
|
+
method_source (1.0.0)
|
16
|
+
minitest (5.18.0)
|
17
|
+
parallel (1.22.1)
|
18
|
+
parser (3.2.2.0)
|
19
|
+
ast (~> 2.4.1)
|
20
|
+
rainbow (3.1.1)
|
21
|
+
rake (13.0.6)
|
22
|
+
regexp_parser (2.7.0)
|
23
|
+
rexml (3.2.5)
|
24
|
+
rubocop (1.48.1)
|
25
|
+
json (~> 2.3)
|
26
|
+
parallel (~> 1.10)
|
27
|
+
parser (>= 3.2.0.0)
|
28
|
+
rainbow (>= 2.2.2, < 4.0)
|
29
|
+
regexp_parser (>= 1.8, < 3.0)
|
30
|
+
rexml (>= 3.2.5, < 4.0)
|
31
|
+
rubocop-ast (>= 1.26.0, < 2.0)
|
32
|
+
ruby-progressbar (~> 1.7)
|
33
|
+
unicode-display_width (>= 2.4.0, < 3.0)
|
34
|
+
rubocop-ast (1.28.0)
|
35
|
+
parser (>= 3.2.1.0)
|
36
|
+
rubocop-performance (1.16.0)
|
37
|
+
rubocop (>= 1.7.0, < 2.0)
|
38
|
+
rubocop-ast (>= 0.4.0)
|
39
|
+
ruby-progressbar (1.13.0)
|
40
|
+
standard (1.26.0)
|
41
|
+
language_server-protocol (~> 3.17.0.2)
|
42
|
+
rubocop (~> 1.48.1)
|
43
|
+
rubocop-performance (~> 1.16.0)
|
44
|
+
unicode-display_width (2.4.2)
|
45
|
+
|
46
|
+
PLATFORMS
|
47
|
+
arm64-darwin-22
|
48
|
+
|
49
|
+
DEPENDENCIES
|
50
|
+
lint_roller!
|
51
|
+
m
|
52
|
+
minitest
|
53
|
+
rake
|
54
|
+
standard
|
55
|
+
|
56
|
+
BUNDLED WITH
|
57
|
+
2.4.10
|
data/LICENSE.txt
ADDED
@@ -0,0 +1,21 @@
|
|
1
|
+
The MIT License (MIT)
|
2
|
+
|
3
|
+
Copyright (c) 2023 Test Double, Inc.
|
4
|
+
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
7
|
+
in the Software without restriction, including without limitation the rights
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
10
|
+
furnished to do so, subject to the following conditions:
|
11
|
+
|
12
|
+
The above copyright notice and this permission notice shall be included in
|
13
|
+
all copies or substantial portions of the Software.
|
14
|
+
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
21
|
+
THE SOFTWARE.
|
data/README.md
ADDED
@@ -0,0 +1,176 @@
|
|
1
|
+
# lint_roller - A plugin specification for linters
|
2
|
+
|
3
|
+
`lint_roller` is an itty-bitty plugin API for code analysis tools like linters
|
4
|
+
and formatters. It provides plugins for those tools to load extensions and
|
5
|
+
specify custom rulesets.
|
6
|
+
|
7
|
+
(As of this release, only [Standard
|
8
|
+
Ruby](https://github.com/standardrb/standard) supports `lint_roller` plugins,
|
9
|
+
but we think [RuboCop](https://github.com/rubocop/rubocop) could add support and
|
10
|
+
most plugins would be compatible with both `rubocop` and `standardrb`.
|
11
|
+
Additionally, there's nothing that would prevent other tools like
|
12
|
+
[rufo](https://github.com/ruby-formatter/rufo) from adopting it.)
|
13
|
+
|
14
|
+
## How to make a plugin
|
15
|
+
|
16
|
+
If you want to make a plugin, the first thing you should do is extend
|
17
|
+
[LintRoller::Plugin](/lib/lint_roller/plugin.rb) with a custom class. Let's take
|
18
|
+
this example plugin for banana-related static analysis:
|
19
|
+
|
20
|
+
```ruby
|
21
|
+
module BananaRoller
|
22
|
+
class Plugin
|
23
|
+
# `config' is a Hash of options passed to the plugin by the user
|
24
|
+
def initialize(config = {})
|
25
|
+
@alternative = config["alternative"] ||= "chocolate"
|
26
|
+
end
|
27
|
+
|
28
|
+
def about
|
29
|
+
LintRoller::About.new(
|
30
|
+
name: "banana_roller",
|
31
|
+
version: "1.0", # or, in a gem, probably BananaRoller::VERSION
|
32
|
+
homepage: "https://github.com/example/banana_roller",
|
33
|
+
description: "Configuration of banana-related code"
|
34
|
+
)
|
35
|
+
end
|
36
|
+
|
37
|
+
# `context' is an instance of LintRoller::Context provided by the runner
|
38
|
+
def supported?(context)
|
39
|
+
if context.engine == :rubocop
|
40
|
+
true
|
41
|
+
else
|
42
|
+
false
|
43
|
+
end
|
44
|
+
end
|
45
|
+
|
46
|
+
# `context' is an instance of LintRoller::Context provided by the runner
|
47
|
+
def rules(context)
|
48
|
+
LintRoller::Rules.new(
|
49
|
+
type: :path,
|
50
|
+
config_format: :rubocop,
|
51
|
+
value: Pathname.new(__dir__).join("../../config/default.yml")
|
52
|
+
)
|
53
|
+
end
|
54
|
+
end
|
55
|
+
end
|
56
|
+
```
|
57
|
+
|
58
|
+
And that's pretty much it. Just a declarative way to identify your plugin,
|
59
|
+
detect whether it supports the given context (e.g. the current `runner` and
|
60
|
+
`engine` and their respective `_version`s), and then provides your custom
|
61
|
+
configuration as a [LintRoller::Rules](lib/lint_roller/rules.rb) object.
|
62
|
+
|
63
|
+
## Packaging a plugin in a gem
|
64
|
+
|
65
|
+
In order for a formatter to use your plugin, it needs to know where to what path
|
66
|
+
to require and the name of your plugin class to instantiate and invoke.
|
67
|
+
|
68
|
+
To make this work seamlessly for your users without additional configuration of
|
69
|
+
their own, all you need to do is specify a metadata attribute called
|
70
|
+
`default_lint_roller_plugin` in your gemspec.
|
71
|
+
|
72
|
+
Taking [standard-custom](https://github.com/standardrb/standard-custom) as an
|
73
|
+
example, its gemspec contains:
|
74
|
+
|
75
|
+
```ruby
|
76
|
+
Gem::Specification.new do |spec|
|
77
|
+
# …
|
78
|
+
spec.metadata["default_lint_roller_plugin"] = "Standard::Custom::Plugin"
|
79
|
+
# …
|
80
|
+
end
|
81
|
+
```
|
82
|
+
|
83
|
+
Because gem specs are loaded by RubyGems and Bundler very early, remember to
|
84
|
+
specify the plugin as a string representation of the constant, as load order
|
85
|
+
usually matters, and most tools will need to be loaded before any custom
|
86
|
+
extensions. Hence, `"Standard::Custom::Plugin"` instead of
|
87
|
+
`Standard::Custom::Plugin`.
|
88
|
+
|
89
|
+
## Using your plugin
|
90
|
+
|
91
|
+
Once you've made your plugin, here's how it's configured from a Standard Ruby
|
92
|
+
`.standard.yml` file.
|
93
|
+
|
94
|
+
### If your plugin is packaged as a gem
|
95
|
+
|
96
|
+
Packaging your plugin in a gem is the golden path, both because distributing
|
97
|
+
code via [RubyGems.org](https://rubygems.org) is very neat, but also because it
|
98
|
+
makes the least work for your users.
|
99
|
+
|
100
|
+
If your gem name is `banana_roller` and you've set
|
101
|
+
`spec.metadata["default_lint_roller_plugin"]` to `"BananaRoller::Plugin"`, then
|
102
|
+
your users could just add this to their `.standard.yml` file:
|
103
|
+
|
104
|
+
```yaml
|
105
|
+
plugins:
|
106
|
+
- banana_roller
|
107
|
+
```
|
108
|
+
|
109
|
+
And that's it! During initialization, `standardrb` will `require
|
110
|
+
"banana_roller"` and know to call `BananaRoller::Plugin.new(config)` to
|
111
|
+
instantiate it.
|
112
|
+
|
113
|
+
### If your plugin ISN'T in a gem
|
114
|
+
|
115
|
+
If you're developing a plugin for internal use or in conjunction with a single
|
116
|
+
project, you may want it to live in the same repo as opposed to packaging it in
|
117
|
+
a gem.
|
118
|
+
|
119
|
+
To do this, then—in lieu of a gem name—provide the path you want to be required
|
120
|
+
as its name, and (since there is no `spec.metadata` to learn of your plugin's
|
121
|
+
class name), specify it as an option on the plugin:
|
122
|
+
|
123
|
+
```yaml
|
124
|
+
plugins:
|
125
|
+
- lib/banana_roller/plugin:
|
126
|
+
plugin_class_name: BananaRoller::Plugin
|
127
|
+
```
|
128
|
+
|
129
|
+
(Be careful with the indentation here! Any configuration under a plugin must be
|
130
|
+
indented in order for it to be parsed as a hash under the
|
131
|
+
`"lib/banana_roller/plugin"` key.)
|
132
|
+
|
133
|
+
Additionally, if you want the plugin's name to make more sense, you can give
|
134
|
+
it whatever name you like in the configuration and specify the `require_path`
|
135
|
+
explicitly:
|
136
|
+
|
137
|
+
```yaml
|
138
|
+
plugins:
|
139
|
+
- banana_roller:
|
140
|
+
require_path: lib/banana_roller/plugin
|
141
|
+
plugin_class_name: BananaRoller::Plugin
|
142
|
+
```
|
143
|
+
|
144
|
+
### Passing user configuration to the plugin
|
145
|
+
|
146
|
+
When a `LintRoller::Plugin` is instantiated, users can pass a configuration hash
|
147
|
+
that tells your plugin how to behave.
|
148
|
+
|
149
|
+
To illustrate how this works in Standard Ruby, anything passed as a hash beneath
|
150
|
+
a plugin will be passed to the class's `initialize` method:
|
151
|
+
|
152
|
+
```yaml
|
153
|
+
plugins:
|
154
|
+
- apple_roller
|
155
|
+
- banana_roller:
|
156
|
+
require_path: lib/banana_roller/plugin
|
157
|
+
plugin_class_name: BananaRoller::Plugin
|
158
|
+
alternative: "apples"
|
159
|
+
- orange_roller:
|
160
|
+
rind: false
|
161
|
+
```
|
162
|
+
|
163
|
+
In the above case, `apple_roller`'s plugin class will be instantiated with
|
164
|
+
`new({})`, `banana_roller` will get all 3 of those parameters passed
|
165
|
+
`BananaRoller::Plugin.new({require_path…})`, and `orange_roller`'s class will be
|
166
|
+
called with `new({rind: false})`.
|
167
|
+
|
168
|
+
## Code of Conduct
|
169
|
+
|
170
|
+
This project follows Test Double's [code of
|
171
|
+
conduct](https://testdouble.com/code-of-conduct) for all community interactions,
|
172
|
+
including (but not limited to) one-on-one communications, public posts/comments,
|
173
|
+
code reviews, pull requests, and GitHub issues. If violations occur, Test Double
|
174
|
+
will take any action they deem appropriate for the infraction, up to and
|
175
|
+
including blocking a user from the organization's repositories.
|
176
|
+
|
data/Rakefile
ADDED
@@ -0,0 +1,9 @@
|
|
1
|
+
module LintRoller
|
2
|
+
About = Struct.new(
|
3
|
+
:name, # "standard-performance"
|
4
|
+
:version, # "1.2.3"
|
5
|
+
:homepage, # "https://github.com/testdouble/standard-performance"
|
6
|
+
:description, # "A configuration of rubocop-performance rules to make Ruby go faster"
|
7
|
+
keyword_init: true
|
8
|
+
)
|
9
|
+
end
|
@@ -0,0 +1,11 @@
|
|
1
|
+
module LintRoller
|
2
|
+
Context = Struct.new(
|
3
|
+
:runner, # :standard, :rubocop
|
4
|
+
:runner_version, # "1.2.3"
|
5
|
+
:engine, # :rubocop
|
6
|
+
:engine_version, # "2.3.4",
|
7
|
+
:rule_format, # :rubocop
|
8
|
+
:target_ruby_version, # Gem::Version.new("2.7.0")
|
9
|
+
keyword_init: true
|
10
|
+
)
|
11
|
+
end
|
@@ -0,0 +1,22 @@
|
|
1
|
+
module LintRoller
|
2
|
+
class Plugin
|
3
|
+
# `config' is a Hash of options passed to the plugin by the user
|
4
|
+
def initialize(config = {})
|
5
|
+
@config = config
|
6
|
+
end
|
7
|
+
|
8
|
+
def about
|
9
|
+
raise Error.new("Please implement `about` and return an instance of LintRoller::About")
|
10
|
+
end
|
11
|
+
|
12
|
+
# `context' is an instance of LintRoller::Context provided by the runner
|
13
|
+
def supported?(context)
|
14
|
+
true
|
15
|
+
end
|
16
|
+
|
17
|
+
# `context' is an instance of LintRoller::Context provided by the runner
|
18
|
+
def rules(context)
|
19
|
+
raise Error.new("Please implement `rules(context)` and return an instance of LintRoller::Rules")
|
20
|
+
end
|
21
|
+
end
|
22
|
+
end
|
@@ -0,0 +1,17 @@
|
|
1
|
+
module LintRoller
|
2
|
+
Rules = Struct.new(
|
3
|
+
# Valid values: :path, :object, :error
|
4
|
+
:type,
|
5
|
+
# Only known value right now is :rubocop but nothing would stop rufo or
|
6
|
+
# rubyfmt or prettier from adding support without a change to the gem
|
7
|
+
:config_format,
|
8
|
+
# If type is :path, String or Pathname. Otherwise, whatever :object type
|
9
|
+
# makes sense given :config_format (e.g. for RuboCop, a Hash loaded from a
|
10
|
+
# YAML file; note that providing a hash will prevent the use of RuboCop features
|
11
|
+
# like `inherit_from' and `require'!)
|
12
|
+
:value,
|
13
|
+
# If something went wrong an Error for the runner to deal with appropriately
|
14
|
+
:error,
|
15
|
+
keyword_init: true
|
16
|
+
)
|
17
|
+
end
|
data/lib/lint_roller.rb
ADDED
@@ -0,0 +1,11 @@
|
|
1
|
+
require_relative "lint_roller/version"
|
2
|
+
|
3
|
+
require_relative "lint_roller/about"
|
4
|
+
require_relative "lint_roller/context"
|
5
|
+
require_relative "lint_roller/rules"
|
6
|
+
|
7
|
+
require_relative "lint_roller/plugin"
|
8
|
+
require_relative "lint_roller/error"
|
9
|
+
|
10
|
+
module LintRoller
|
11
|
+
end
|
metadata
ADDED
@@ -0,0 +1,60 @@
|
|
1
|
+
--- !ruby/object:Gem::Specification
|
2
|
+
name: lint_roller
|
3
|
+
version: !ruby/object:Gem::Version
|
4
|
+
version: 1.0.0
|
5
|
+
platform: ruby
|
6
|
+
authors:
|
7
|
+
- Justin Searls
|
8
|
+
autorequire:
|
9
|
+
bindir: exe
|
10
|
+
cert_chain: []
|
11
|
+
date: 2023-04-15 00:00:00.000000000 Z
|
12
|
+
dependencies: []
|
13
|
+
description:
|
14
|
+
email:
|
15
|
+
- searls@gmail.com
|
16
|
+
executables: []
|
17
|
+
extensions: []
|
18
|
+
extra_rdoc_files: []
|
19
|
+
files:
|
20
|
+
- ".standard.yml"
|
21
|
+
- CHANGELOG.md
|
22
|
+
- Gemfile
|
23
|
+
- Gemfile.lock
|
24
|
+
- LICENSE.txt
|
25
|
+
- README.md
|
26
|
+
- Rakefile
|
27
|
+
- lib/lint_roller.rb
|
28
|
+
- lib/lint_roller/about.rb
|
29
|
+
- lib/lint_roller/context.rb
|
30
|
+
- lib/lint_roller/error.rb
|
31
|
+
- lib/lint_roller/plugin.rb
|
32
|
+
- lib/lint_roller/rules.rb
|
33
|
+
- lib/lint_roller/version.rb
|
34
|
+
homepage: https://github.com/standardrb/lint_roller
|
35
|
+
licenses:
|
36
|
+
- MIT
|
37
|
+
metadata:
|
38
|
+
homepage_uri: https://github.com/standardrb/lint_roller
|
39
|
+
source_code_uri: https://github.com/standardrb/lint_roller
|
40
|
+
changelog_uri: https://github.com/standardrb/lint_roller/blob/main/CHANGELOG.md
|
41
|
+
post_install_message:
|
42
|
+
rdoc_options: []
|
43
|
+
require_paths:
|
44
|
+
- lib
|
45
|
+
required_ruby_version: !ruby/object:Gem::Requirement
|
46
|
+
requirements:
|
47
|
+
- - ">="
|
48
|
+
- !ruby/object:Gem::Version
|
49
|
+
version: 2.6.0
|
50
|
+
required_rubygems_version: !ruby/object:Gem::Requirement
|
51
|
+
requirements:
|
52
|
+
- - ">="
|
53
|
+
- !ruby/object:Gem::Version
|
54
|
+
version: '0'
|
55
|
+
requirements: []
|
56
|
+
rubygems_version: 3.4.10
|
57
|
+
signing_key:
|
58
|
+
specification_version: 4
|
59
|
+
summary: A plugin specification for linter and formatter rulesets
|
60
|
+
test_files: []
|