lcgstyle 0.0.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.gitignore +9 -0
- data/.rspec +2 -0
- data/.travis.yml +4 -0
- data/Gemfile +4 -0
- data/LICENSE.txt +201 -0
- data/README.md +106 -0
- data/Rakefile +28 -0
- data/bin/lcgstyle +13 -0
- data/config/chefstyle.yml +370 -0
- data/config/default.yml +3 -0
- data/config/disable_all.yml +557 -0
- data/config/disabled.yml +125 -0
- data/config/enabled.yml +1352 -0
- data/config/upstream.yml +1118 -0
- data/lcgstyle.gemspec +25 -0
- data/lib/lcgstyle/version.rb +4 -0
- data/lib/lcgstyle.rb +29 -0
- metadata +118 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA1:
|
3
|
+
metadata.gz: 2078eb195eb828f2bcc4d02b8598f4f07882cc2f
|
4
|
+
data.tar.gz: d7a5013bf728e5b0370c29ab6ea2fa3528821321
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: 6eff1735c11a9cfa6838b89ac2b0e447765f5026e6012fec127cae8a8ea585cac21c30f416dd22fe8d3646cc4a6a4386c3cf092885b8f8287bd08f9d0caaa9fd
|
7
|
+
data.tar.gz: a3bde6800c7603cd0d2a00973635844f51105d8cb851e7235344e3532a2a97f3772946c606b7046e63ff431dbb897876b64b618682303917919f2a0e202e20bb
|
data/.gitignore
ADDED
data/.rspec
ADDED
data/.travis.yml
ADDED
data/Gemfile
ADDED
data/LICENSE.txt
ADDED
@@ -0,0 +1,201 @@
|
|
1
|
+
Apache License
|
2
|
+
Version 2.0, January 2004
|
3
|
+
http://www.apache.org/licenses/
|
4
|
+
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
6
|
+
|
7
|
+
1. Definitions.
|
8
|
+
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
11
|
+
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
13
|
+
the copyright owner that is granting the License.
|
14
|
+
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
16
|
+
other entities that control, are controlled by, or are under common
|
17
|
+
control with that entity. For the purposes of this definition,
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
19
|
+
direction or management of such entity, whether by contract or
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
22
|
+
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
24
|
+
exercising permissions granted by this License.
|
25
|
+
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
27
|
+
including but not limited to software source code, documentation
|
28
|
+
source, and configuration files.
|
29
|
+
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
31
|
+
transformation or translation of a Source form, including but
|
32
|
+
not limited to compiled object code, generated documentation,
|
33
|
+
and conversions to other media types.
|
34
|
+
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
36
|
+
Object form, made available under the License, as indicated by a
|
37
|
+
copyright notice that is included in or attached to the work
|
38
|
+
(an example is provided in the Appendix below).
|
39
|
+
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
46
|
+
the Work and Derivative Works thereof.
|
47
|
+
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
49
|
+
the original version of the Work and any modifications or additions
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
61
|
+
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
64
|
+
subsequently incorporated within the Work.
|
65
|
+
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
72
|
+
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
78
|
+
where such license applies only to those patent claims licensable
|
79
|
+
by such Contributor that are necessarily infringed by their
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
82
|
+
institute patent litigation against any entity (including a
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
85
|
+
or contributory patent infringement, then any patent licenses
|
86
|
+
granted to You under this License for that Work shall terminate
|
87
|
+
as of the date such litigation is filed.
|
88
|
+
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
91
|
+
modifications, and in Source or Object form, provided that You
|
92
|
+
meet the following conditions:
|
93
|
+
|
94
|
+
(a) You must give any other recipients of the Work or
|
95
|
+
Derivative Works a copy of this License; and
|
96
|
+
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
98
|
+
stating that You changed the files; and
|
99
|
+
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
102
|
+
attribution notices from the Source form of the Work,
|
103
|
+
excluding those notices that do not pertain to any part of
|
104
|
+
the Derivative Works; and
|
105
|
+
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
108
|
+
include a readable copy of the attribution notices contained
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
111
|
+
of the following places: within a NOTICE text file distributed
|
112
|
+
as part of the Derivative Works; within the Source form or
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
114
|
+
within a display generated by the Derivative Works, if and
|
115
|
+
wherever such third-party notices normally appear. The contents
|
116
|
+
of the NOTICE file are for informational purposes only and
|
117
|
+
do not modify the License. You may add Your own attribution
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
120
|
+
that such additional attribution notices cannot be construed
|
121
|
+
as modifying the License.
|
122
|
+
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
124
|
+
may provide additional or different license terms and conditions
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
128
|
+
the conditions stated in this License.
|
129
|
+
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
133
|
+
this License, without any additional terms or conditions.
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
135
|
+
the terms of any separate license agreement you may have executed
|
136
|
+
with Licensor regarding such Contributions.
|
137
|
+
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
140
|
+
except as required for reasonable and customary use in describing the
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
142
|
+
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
152
|
+
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
158
|
+
incidental, or consequential damages of any character arising as a
|
159
|
+
result of this License or out of the use or inability to use the
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
162
|
+
other commercial damages or losses), even if such Contributor
|
163
|
+
has been advised of the possibility of such damages.
|
164
|
+
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
168
|
+
or other liability obligations and/or rights consistent with this
|
169
|
+
License. However, in accepting such obligations, You may act only
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
174
|
+
of your accepting any such warranty or additional liability.
|
175
|
+
|
176
|
+
END OF TERMS AND CONDITIONS
|
177
|
+
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
179
|
+
|
180
|
+
To apply the Apache License to your work, attach the following
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
182
|
+
replaced with your own identifying information. (Don't include
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
184
|
+
comment syntax for the file format. We also recommend that a
|
185
|
+
file or class name and description of purpose be included on the
|
186
|
+
same "printed page" as the copyright notice for easier
|
187
|
+
identification within third-party archives.
|
188
|
+
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
190
|
+
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
192
|
+
you may not use this file except in compliance with the License.
|
193
|
+
You may obtain a copy of the License at
|
194
|
+
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
196
|
+
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
200
|
+
See the License for the specific language governing permissions and
|
201
|
+
limitations under the License.
|
data/README.md
ADDED
@@ -0,0 +1,106 @@
|
|
1
|
+
# Lcgstyle - Version Pinned rubocop and sane defaults for Ruby
|
2
|
+
|
3
|
+
This is an internal style guide for chef ruby projects (chef-client,
|
4
|
+
ohai, mixlib-shellout, mixlib-config, etc).
|
5
|
+
|
6
|
+
It is not meant for consumption by cookbooks or for any general
|
7
|
+
purpose uses. It is not intended for any audience outside of chef
|
8
|
+
core ruby development.
|
9
|
+
|
10
|
+
It will have many rules that are disabled simply because fixing a
|
11
|
+
project as large as chef-client would be tedious and have little
|
12
|
+
value. It will have other rules that are disabled because chef
|
13
|
+
exposes edge conditions that make them falsely alert. Other rules
|
14
|
+
will be selected based on the biases of the core chef developers
|
15
|
+
which are often violently at odds with the rubocop core developers
|
16
|
+
over ruby style.
|
17
|
+
|
18
|
+
Pull requests to this repo will not be accepted without corresponding
|
19
|
+
PRs into at least the chef-client and ohai codebases to clean the
|
20
|
+
code up. PRs will not be accepted that assume unfunded mandates for
|
21
|
+
other people to finish the work. Do not open PRs offering opinions
|
22
|
+
or suggestions without offering to do the work.
|
23
|
+
|
24
|
+
The project itself is a derivative of
|
25
|
+
[finstyle](https://github.com/fnichol/finstyle), but starts with all
|
26
|
+
rules disabled. The active ruleset is in the
|
27
|
+
[config/lcgstyle.yml](https://github.com/chef/lcgstyle/blob/master/config/lcgstyle.yml)
|
28
|
+
file.
|
29
|
+
|
30
|
+
## How It Works
|
31
|
+
|
32
|
+
This library has a direct dependency on one specific version of RuboCop (at a time), and [patches it][patch] to load the [upstream configuration][upstream] and [custom set][config] of rule updates. When a new RuboCop release comes out, this library can rev its pinned version dependency and [re-vendor][rakefile] the upstream configuration to determine if any breaking style or lint rules were added/dropped/reversed/etc.
|
33
|
+
|
34
|
+
## Installation
|
35
|
+
|
36
|
+
Add this line to your application's Gemfile:
|
37
|
+
|
38
|
+
```ruby
|
39
|
+
gem 'lcgstyle'
|
40
|
+
```
|
41
|
+
|
42
|
+
And then execute:
|
43
|
+
|
44
|
+
$ bundle
|
45
|
+
|
46
|
+
Or install it yourself as:
|
47
|
+
|
48
|
+
$ gem install lcgstyle
|
49
|
+
|
50
|
+
## Usage
|
51
|
+
|
52
|
+
### Vanilla RuboCop
|
53
|
+
|
54
|
+
Run RuboCop as normal, simply add a `-r lcgstyle` option when running:
|
55
|
+
|
56
|
+
```sh
|
57
|
+
rubocop -r lcgstyle -D --format offenses
|
58
|
+
```
|
59
|
+
|
60
|
+
### lcgstyle Command
|
61
|
+
|
62
|
+
Use this tool just as you would RuboCop, but invoke the `lcgstyle` binary
|
63
|
+
instead which patches RuboCop to load rules from the lcgstyle gem. For example:
|
64
|
+
|
65
|
+
```sh
|
66
|
+
lcgstyle -D --format offenses
|
67
|
+
```
|
68
|
+
|
69
|
+
### Rake
|
70
|
+
|
71
|
+
In a Rakefile, the setup is exactly the same, except you need to require the
|
72
|
+
lcgstyle library first:
|
73
|
+
|
74
|
+
```ruby
|
75
|
+
require "lcgstyle"
|
76
|
+
require "rubocop/rake_task"
|
77
|
+
RuboCop::RakeTask.new do |task|
|
78
|
+
task.options << "--display-cop-names"
|
79
|
+
end
|
80
|
+
```
|
81
|
+
|
82
|
+
### guard-rubocop
|
83
|
+
|
84
|
+
You can use one of two methods. The simplest is to add the `-r lcgstyle` option to the `:cli` option in your Guardfile:
|
85
|
+
|
86
|
+
```ruby
|
87
|
+
guard :rubocop, cli: "-r lcgstyle" do
|
88
|
+
watch(%r{.+\.rb$})
|
89
|
+
watch(%r{(?:.+/)?\.rubocop\.yml$}) { |m| File.dirname(m[0]) }
|
90
|
+
end
|
91
|
+
```
|
92
|
+
|
93
|
+
Alternatively you could pass the path to Lcgstyle's configuration by using the `Lcgstyle.config` method:
|
94
|
+
|
95
|
+
```ruby
|
96
|
+
require "lcgstyle"
|
97
|
+
|
98
|
+
guard :rubocop, cli: "--config #{Lcgstyle.config}" do
|
99
|
+
watch(%r{.+\.rb$})
|
100
|
+
watch(%r{(?:.+/)?\.rubocop\.yml$}) { |m| File.dirname(m[0]) }
|
101
|
+
end
|
102
|
+
```
|
103
|
+
|
104
|
+
### .rubocop.yml
|
105
|
+
|
106
|
+
As with vanilla RuboCop, any custom settings can still be placed in a `.rubocop.yml` file in the root of your project.
|
data/Rakefile
ADDED
@@ -0,0 +1,28 @@
|
|
1
|
+
require "bundler/gem_tasks"
|
2
|
+
|
3
|
+
upstream = Gem::Specification.find_by_name("rubocop")
|
4
|
+
|
5
|
+
desc "Vendor rubocop-#{upstream.version} configuration into gem"
|
6
|
+
task :vendor do
|
7
|
+
src = Pathname.new(upstream.gem_dir).join("config")
|
8
|
+
dst = Pathname.new(__FILE__).dirname.join("config")
|
9
|
+
|
10
|
+
mkdir_p dst
|
11
|
+
cp(src.join("default.yml"), dst.join("upstream.yml"))
|
12
|
+
cp(src.join("enabled.yml"), dst.join("enabled.yml"))
|
13
|
+
cp(src.join("disabled.yml"), dst.join("disabled.yml"))
|
14
|
+
|
15
|
+
require "rubocop"
|
16
|
+
require "yaml"
|
17
|
+
cfg = RuboCop::Cop::Cop.all.each_with_object({}) { |acc, cop| acc[cop.cop_name] = { "Enabled" => false } }
|
18
|
+
File.open(dst.join("disable_all.yml"), "w") { |fh| fh.write cfg.to_yaml }
|
19
|
+
|
20
|
+
sh %{git add #{dst}/{upstream,enabled,disabled,disable_all}.yml}
|
21
|
+
sh %{git commit -m "Vendor rubocop-#{upstream.version} upstream configuration."}
|
22
|
+
end
|
23
|
+
|
24
|
+
require "lcgstyle"
|
25
|
+
require "rubocop/rake_task"
|
26
|
+
RuboCop::RakeTask.new(:style) do |task|
|
27
|
+
task.options << "--display-cop-names"
|
28
|
+
end
|
data/bin/lcgstyle
ADDED
@@ -0,0 +1,13 @@
|
|
1
|
+
#!/usr/bin/env ruby
|
2
|
+
# -*- encoding: utf-8 -*-
|
3
|
+
|
4
|
+
$LOAD_PATH.unshift File.join(File.dirname(__FILE__), %w{.. lib})
|
5
|
+
|
6
|
+
require "lcgstyle"
|
7
|
+
|
8
|
+
if ARGV.size == 1 && %w{-v --version}.include?(ARGV.first)
|
9
|
+
puts "Lcgstyle #{Lcgstyle::VERSION}"
|
10
|
+
print " * RuboCop "
|
11
|
+
end
|
12
|
+
|
13
|
+
load Gem.bin_path("rubocop", "rubocop")
|