rubocop-digitalhospital 0.2.0 → 0.3.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/.github/dependabot.yml +0 -0
- data/.gitignore +11 -11
- data/.rspec +3 -3
- data/.rubocop.yml +3 -3
- data/.rubocop_todo.yml +7 -7
- data/.travis.yml +6 -6
- data/CODE_OF_CONDUCT.md +74 -74
- data/Gemfile +1 -1
- data/Gemfile.lock +40 -41
- data/LICENSE.txt +21 -21
- data/README.md +44 -44
- data/Rakefile +8 -8
- data/bin/console +14 -14
- data/bin/setup +8 -8
- data/lib/rubocop/digitalhospital/version.rb +1 -1
- data/lib/rubocop/digitalhospital.rb +10 -10
- data/rubocop-all.yml +2 -2
- data/rubocop-bundler.yml +3 -3
- data/rubocop-default.yml +18 -18
- data/rubocop-digitalhospital.gemspec +41 -40
- data/rubocop-gemspec.yml +5 -5
- data/rubocop-layout.yml +4 -4
- data/rubocop-lint.yml +0 -0
- data/rubocop-metrics.yml +42 -42
- data/rubocop-migrations.yml +19 -19
- data/rubocop-naming.yml +0 -0
- data/rubocop-performance.yml +0 -0
- data/rubocop-rails.yml +0 -0
- data/rubocop-rspec.yml +0 -0
- data/rubocop-style.yml +7 -7
- metadata +5 -5
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 579c275820d547da95b1fd9c94ddb29d0fc6025fe5f99eae3e27d29b425ad2c6
|
|
4
|
+
data.tar.gz: 8a12f90b45e23b24fe168e62820c84b8f0dc5d9256fda6d94a4f6b957a741b98
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: df544a6bf1b2ff171dece064399988bbd8fb0438eca776c22dce7c44aacda9677be8c827663ecb69e29831a6074d122b2da02870d566693426bb78aa113faca1
|
|
7
|
+
data.tar.gz: 0dd514c3b4b5ad295219a494f0a75c356a20114932eca9bc05f692fb41bb993e045de039439f5d84951acddf1ae3489fb42b4b79d1fdff26ec2baffda30ecb88
|
data/.github/dependabot.yml
CHANGED
|
File without changes
|
data/.gitignore
CHANGED
|
@@ -1,11 +1,11 @@
|
|
|
1
|
-
/.bundle/
|
|
2
|
-
/.yardoc
|
|
3
|
-
/_yardoc/
|
|
4
|
-
/coverage/
|
|
5
|
-
/doc/
|
|
6
|
-
/pkg/
|
|
7
|
-
/spec/reports/
|
|
8
|
-
/tmp/
|
|
9
|
-
|
|
10
|
-
# rspec failure tracking
|
|
11
|
-
.rspec_status
|
|
1
|
+
/.bundle/
|
|
2
|
+
/.yardoc
|
|
3
|
+
/_yardoc/
|
|
4
|
+
/coverage/
|
|
5
|
+
/doc/
|
|
6
|
+
/pkg/
|
|
7
|
+
/spec/reports/
|
|
8
|
+
/tmp/
|
|
9
|
+
|
|
10
|
+
# rspec failure tracking
|
|
11
|
+
.rspec_status
|
data/.rspec
CHANGED
|
@@ -1,3 +1,3 @@
|
|
|
1
|
-
--format documentation
|
|
2
|
-
--color
|
|
3
|
-
--require spec_helper
|
|
1
|
+
--format documentation
|
|
2
|
+
--color
|
|
3
|
+
--require spec_helper
|
data/.rubocop.yml
CHANGED
|
@@ -1,3 +1,3 @@
|
|
|
1
|
-
inherit_from:
|
|
2
|
-
- rubocop-default.yml
|
|
3
|
-
- .rubocop_todo.yml
|
|
1
|
+
inherit_from:
|
|
2
|
+
- rubocop-default.yml
|
|
3
|
+
- .rubocop_todo.yml
|
data/.rubocop_todo.yml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
|
-
# This configuration was generated by
|
|
2
|
-
# `rubocop --auto-gen-config`
|
|
3
|
-
# on 2017-11-03 15:49:59 +0100 using RuboCop version 0.51.0.
|
|
4
|
-
# The point is for the user to remove these configuration records
|
|
5
|
-
# one by one as the offenses are removed from the code base.
|
|
6
|
-
# Note that changes in the inspected code, or installation of new
|
|
7
|
-
# versions of RuboCop, may require this file to be generated again.
|
|
1
|
+
# This configuration was generated by
|
|
2
|
+
# `rubocop --auto-gen-config`
|
|
3
|
+
# on 2017-11-03 15:49:59 +0100 using RuboCop version 0.51.0.
|
|
4
|
+
# The point is for the user to remove these configuration records
|
|
5
|
+
# one by one as the offenses are removed from the code base.
|
|
6
|
+
# Note that changes in the inspected code, or installation of new
|
|
7
|
+
# versions of RuboCop, may require this file to be generated again.
|
data/.travis.yml
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
---
|
|
2
|
-
language: ruby
|
|
3
|
-
cache: bundler
|
|
4
|
-
rvm:
|
|
5
|
-
- 2.6.5
|
|
6
|
-
before_install: gem install bundler -v 2.1.4
|
|
1
|
+
---
|
|
2
|
+
language: ruby
|
|
3
|
+
cache: bundler
|
|
4
|
+
rvm:
|
|
5
|
+
- 2.6.5
|
|
6
|
+
before_install: gem install bundler -v 2.1.4
|
data/CODE_OF_CONDUCT.md
CHANGED
|
@@ -1,74 +1,74 @@
|
|
|
1
|
-
# Contributor Covenant Code of Conduct
|
|
2
|
-
|
|
3
|
-
## Our Pledge
|
|
4
|
-
|
|
5
|
-
In the interest of fostering an open and welcoming environment, we as
|
|
6
|
-
contributors and maintainers pledge to making participation in our project and
|
|
7
|
-
our community a harassment-free experience for everyone, regardless of age, body
|
|
8
|
-
size, disability, ethnicity, gender identity and expression, level of experience,
|
|
9
|
-
nationality, personal appearance, race, religion, or sexual identity and
|
|
10
|
-
orientation.
|
|
11
|
-
|
|
12
|
-
## Our Standards
|
|
13
|
-
|
|
14
|
-
Examples of behavior that contributes to creating a positive environment
|
|
15
|
-
include:
|
|
16
|
-
|
|
17
|
-
* Using welcoming and inclusive language
|
|
18
|
-
* Being respectful of differing viewpoints and experiences
|
|
19
|
-
* Gracefully accepting constructive criticism
|
|
20
|
-
* Focusing on what is best for the community
|
|
21
|
-
* Showing empathy towards other community members
|
|
22
|
-
|
|
23
|
-
Examples of unacceptable behavior by participants include:
|
|
24
|
-
|
|
25
|
-
* The use of sexualized language or imagery and unwelcome sexual attention or
|
|
26
|
-
advances
|
|
27
|
-
* Trolling, insulting/derogatory comments, and personal or political attacks
|
|
28
|
-
* Public or private harassment
|
|
29
|
-
* Publishing others' private information, such as a physical or electronic
|
|
30
|
-
address, without explicit permission
|
|
31
|
-
* Other conduct which could reasonably be considered inappropriate in a
|
|
32
|
-
professional setting
|
|
33
|
-
|
|
34
|
-
## Our Responsibilities
|
|
35
|
-
|
|
36
|
-
Project maintainers are responsible for clarifying the standards of acceptable
|
|
37
|
-
behavior and are expected to take appropriate and fair corrective action in
|
|
38
|
-
response to any instances of unacceptable behavior.
|
|
39
|
-
|
|
40
|
-
Project maintainers have the right and responsibility to remove, edit, or
|
|
41
|
-
reject comments, commits, code, wiki edits, issues, and other contributions
|
|
42
|
-
that are not aligned to this Code of Conduct, or to ban temporarily or
|
|
43
|
-
permanently any contributor for other behaviors that they deem inappropriate,
|
|
44
|
-
threatening, offensive, or harmful.
|
|
45
|
-
|
|
46
|
-
## Scope
|
|
47
|
-
|
|
48
|
-
This Code of Conduct applies both within project spaces and in public spaces
|
|
49
|
-
when an individual is representing the project or its community. Examples of
|
|
50
|
-
representing a project or community include using an official project e-mail
|
|
51
|
-
address, posting via an official social media account, or acting as an appointed
|
|
52
|
-
representative at an online or offline event. Representation of a project may be
|
|
53
|
-
further defined and clarified by project maintainers.
|
|
54
|
-
|
|
55
|
-
## Enforcement
|
|
56
|
-
|
|
57
|
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
|
58
|
-
reported by contacting the project team at javi@digitalhospital.com. All
|
|
59
|
-
complaints will be reviewed and investigated and will result in a response that
|
|
60
|
-
is deemed necessary and appropriate to the circumstances. The project team is
|
|
61
|
-
obligated to maintain confidentiality with regard to the reporter of an incident.
|
|
62
|
-
Further details of specific enforcement policies may be posted separately.
|
|
63
|
-
|
|
64
|
-
Project maintainers who do not follow or enforce the Code of Conduct in good
|
|
65
|
-
faith may face temporary or permanent repercussions as determined by other
|
|
66
|
-
members of the project's leadership.
|
|
67
|
-
|
|
68
|
-
## Attribution
|
|
69
|
-
|
|
70
|
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
|
71
|
-
available at [https://contributor-covenant.org/version/1/4][version]
|
|
72
|
-
|
|
73
|
-
[homepage]: https://contributor-covenant.org
|
|
74
|
-
[version]: https://contributor-covenant.org/version/1/4/
|
|
1
|
+
# Contributor Covenant Code of Conduct
|
|
2
|
+
|
|
3
|
+
## Our Pledge
|
|
4
|
+
|
|
5
|
+
In the interest of fostering an open and welcoming environment, we as
|
|
6
|
+
contributors and maintainers pledge to making participation in our project and
|
|
7
|
+
our community a harassment-free experience for everyone, regardless of age, body
|
|
8
|
+
size, disability, ethnicity, gender identity and expression, level of experience,
|
|
9
|
+
nationality, personal appearance, race, religion, or sexual identity and
|
|
10
|
+
orientation.
|
|
11
|
+
|
|
12
|
+
## Our Standards
|
|
13
|
+
|
|
14
|
+
Examples of behavior that contributes to creating a positive environment
|
|
15
|
+
include:
|
|
16
|
+
|
|
17
|
+
* Using welcoming and inclusive language
|
|
18
|
+
* Being respectful of differing viewpoints and experiences
|
|
19
|
+
* Gracefully accepting constructive criticism
|
|
20
|
+
* Focusing on what is best for the community
|
|
21
|
+
* Showing empathy towards other community members
|
|
22
|
+
|
|
23
|
+
Examples of unacceptable behavior by participants include:
|
|
24
|
+
|
|
25
|
+
* The use of sexualized language or imagery and unwelcome sexual attention or
|
|
26
|
+
advances
|
|
27
|
+
* Trolling, insulting/derogatory comments, and personal or political attacks
|
|
28
|
+
* Public or private harassment
|
|
29
|
+
* Publishing others' private information, such as a physical or electronic
|
|
30
|
+
address, without explicit permission
|
|
31
|
+
* Other conduct which could reasonably be considered inappropriate in a
|
|
32
|
+
professional setting
|
|
33
|
+
|
|
34
|
+
## Our Responsibilities
|
|
35
|
+
|
|
36
|
+
Project maintainers are responsible for clarifying the standards of acceptable
|
|
37
|
+
behavior and are expected to take appropriate and fair corrective action in
|
|
38
|
+
response to any instances of unacceptable behavior.
|
|
39
|
+
|
|
40
|
+
Project maintainers have the right and responsibility to remove, edit, or
|
|
41
|
+
reject comments, commits, code, wiki edits, issues, and other contributions
|
|
42
|
+
that are not aligned to this Code of Conduct, or to ban temporarily or
|
|
43
|
+
permanently any contributor for other behaviors that they deem inappropriate,
|
|
44
|
+
threatening, offensive, or harmful.
|
|
45
|
+
|
|
46
|
+
## Scope
|
|
47
|
+
|
|
48
|
+
This Code of Conduct applies both within project spaces and in public spaces
|
|
49
|
+
when an individual is representing the project or its community. Examples of
|
|
50
|
+
representing a project or community include using an official project e-mail
|
|
51
|
+
address, posting via an official social media account, or acting as an appointed
|
|
52
|
+
representative at an online or offline event. Representation of a project may be
|
|
53
|
+
further defined and clarified by project maintainers.
|
|
54
|
+
|
|
55
|
+
## Enforcement
|
|
56
|
+
|
|
57
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
|
58
|
+
reported by contacting the project team at javi@digitalhospital.com. All
|
|
59
|
+
complaints will be reviewed and investigated and will result in a response that
|
|
60
|
+
is deemed necessary and appropriate to the circumstances. The project team is
|
|
61
|
+
obligated to maintain confidentiality with regard to the reporter of an incident.
|
|
62
|
+
Further details of specific enforcement policies may be posted separately.
|
|
63
|
+
|
|
64
|
+
Project maintainers who do not follow or enforce the Code of Conduct in good
|
|
65
|
+
faith may face temporary or permanent repercussions as determined by other
|
|
66
|
+
members of the project's leadership.
|
|
67
|
+
|
|
68
|
+
## Attribution
|
|
69
|
+
|
|
70
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
|
71
|
+
available at [https://contributor-covenant.org/version/1/4][version]
|
|
72
|
+
|
|
73
|
+
[homepage]: https://contributor-covenant.org
|
|
74
|
+
[version]: https://contributor-covenant.org/version/1/4/
|
data/Gemfile
CHANGED
data/Gemfile.lock
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
PATH
|
|
2
2
|
remote: .
|
|
3
3
|
specs:
|
|
4
|
-
rubocop-digitalhospital (0.
|
|
4
|
+
rubocop-digitalhospital (0.3.0)
|
|
5
5
|
rubocop
|
|
6
6
|
rubocop-performance
|
|
7
7
|
rubocop-rails
|
|
@@ -10,65 +10,64 @@ PATH
|
|
|
10
10
|
GEM
|
|
11
11
|
remote: https://rubygems.org/
|
|
12
12
|
specs:
|
|
13
|
-
activesupport (
|
|
13
|
+
activesupport (7.0.4)
|
|
14
14
|
concurrent-ruby (~> 1.0, >= 1.0.2)
|
|
15
15
|
i18n (>= 1.6, < 2)
|
|
16
16
|
minitest (>= 5.1)
|
|
17
17
|
tzinfo (~> 2.0)
|
|
18
|
-
zeitwerk (~> 2.3)
|
|
19
18
|
ast (2.4.2)
|
|
20
|
-
concurrent-ruby (1.1.
|
|
21
|
-
diff-lcs (1.
|
|
22
|
-
i18n (1.
|
|
19
|
+
concurrent-ruby (1.1.10)
|
|
20
|
+
diff-lcs (1.5.0)
|
|
21
|
+
i18n (1.12.0)
|
|
23
22
|
concurrent-ruby (~> 1.0)
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
23
|
+
json (2.6.3)
|
|
24
|
+
minitest (5.16.3)
|
|
25
|
+
parallel (1.22.1)
|
|
26
|
+
parser (3.1.3.0)
|
|
27
27
|
ast (~> 2.4.1)
|
|
28
|
-
rack (
|
|
29
|
-
rainbow (3.
|
|
30
|
-
rake (13.0.
|
|
31
|
-
regexp_parser (2.
|
|
28
|
+
rack (3.0.2)
|
|
29
|
+
rainbow (3.1.1)
|
|
30
|
+
rake (13.0.6)
|
|
31
|
+
regexp_parser (2.6.1)
|
|
32
32
|
rexml (3.2.5)
|
|
33
|
-
rspec (3.
|
|
34
|
-
rspec-core (~> 3.
|
|
35
|
-
rspec-expectations (~> 3.
|
|
36
|
-
rspec-mocks (~> 3.
|
|
37
|
-
rspec-core (3.
|
|
38
|
-
rspec-support (~> 3.
|
|
39
|
-
rspec-expectations (3.
|
|
33
|
+
rspec (3.12.0)
|
|
34
|
+
rspec-core (~> 3.12.0)
|
|
35
|
+
rspec-expectations (~> 3.12.0)
|
|
36
|
+
rspec-mocks (~> 3.12.0)
|
|
37
|
+
rspec-core (3.12.0)
|
|
38
|
+
rspec-support (~> 3.12.0)
|
|
39
|
+
rspec-expectations (3.12.0)
|
|
40
40
|
diff-lcs (>= 1.2.0, < 2.0)
|
|
41
|
-
rspec-support (~> 3.
|
|
42
|
-
rspec-mocks (3.
|
|
41
|
+
rspec-support (~> 3.12.0)
|
|
42
|
+
rspec-mocks (3.12.1)
|
|
43
43
|
diff-lcs (>= 1.2.0, < 2.0)
|
|
44
|
-
rspec-support (~> 3.
|
|
45
|
-
rspec-support (3.
|
|
46
|
-
rubocop (1.
|
|
44
|
+
rspec-support (~> 3.12.0)
|
|
45
|
+
rspec-support (3.12.0)
|
|
46
|
+
rubocop (1.40.0)
|
|
47
|
+
json (~> 2.3)
|
|
47
48
|
parallel (~> 1.10)
|
|
48
|
-
parser (>= 3.
|
|
49
|
+
parser (>= 3.1.2.1)
|
|
49
50
|
rainbow (>= 2.2.2, < 4.0)
|
|
50
51
|
regexp_parser (>= 1.8, < 3.0)
|
|
51
|
-
rexml
|
|
52
|
-
rubocop-ast (>= 1.
|
|
52
|
+
rexml (>= 3.2.5, < 4.0)
|
|
53
|
+
rubocop-ast (>= 1.23.0, < 2.0)
|
|
53
54
|
ruby-progressbar (~> 1.7)
|
|
54
55
|
unicode-display_width (>= 1.4.0, < 3.0)
|
|
55
|
-
rubocop-ast (1.
|
|
56
|
-
parser (>= 3.
|
|
57
|
-
rubocop-performance (1.
|
|
56
|
+
rubocop-ast (1.24.0)
|
|
57
|
+
parser (>= 3.1.1.0)
|
|
58
|
+
rubocop-performance (1.15.1)
|
|
58
59
|
rubocop (>= 1.7.0, < 2.0)
|
|
59
60
|
rubocop-ast (>= 0.4.0)
|
|
60
|
-
rubocop-rails (2.
|
|
61
|
+
rubocop-rails (2.17.3)
|
|
61
62
|
activesupport (>= 4.2.0)
|
|
62
63
|
rack (>= 1.1)
|
|
63
|
-
rubocop (>= 1.
|
|
64
|
-
rubocop-rspec (2.
|
|
65
|
-
rubocop (~> 1.
|
|
66
|
-
rubocop-ast (>= 1.1.0)
|
|
64
|
+
rubocop (>= 1.33.0, < 2.0)
|
|
65
|
+
rubocop-rspec (2.16.0)
|
|
66
|
+
rubocop (~> 1.33)
|
|
67
67
|
ruby-progressbar (1.11.0)
|
|
68
|
-
tzinfo (2.0.
|
|
68
|
+
tzinfo (2.0.5)
|
|
69
69
|
concurrent-ruby (~> 1.0)
|
|
70
|
-
unicode-display_width (2.
|
|
71
|
-
zeitwerk (2.4.2)
|
|
70
|
+
unicode-display_width (2.3.0)
|
|
72
71
|
|
|
73
72
|
PLATFORMS
|
|
74
73
|
ruby
|
|
@@ -76,8 +75,8 @@ PLATFORMS
|
|
|
76
75
|
DEPENDENCIES
|
|
77
76
|
bundler
|
|
78
77
|
rake (~> 13.0)
|
|
79
|
-
rspec (~> 3.
|
|
78
|
+
rspec (~> 3.12)
|
|
80
79
|
rubocop-digitalhospital!
|
|
81
80
|
|
|
82
81
|
BUNDLED WITH
|
|
83
|
-
2.
|
|
82
|
+
2.3.8
|
data/LICENSE.txt
CHANGED
|
@@ -1,21 +1,21 @@
|
|
|
1
|
-
The MIT License (MIT)
|
|
2
|
-
|
|
3
|
-
Copyright (c)
|
|
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.
|
|
1
|
+
The MIT License (MIT)
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2022 hectormf
|
|
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
CHANGED
|
@@ -1,44 +1,44 @@
|
|
|
1
|
-
# Rubocop::Digitalhospital
|
|
2
|
-
|
|
3
|
-
Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/rubocop/digitalhospital`. To experiment with that code, run `bin/console` for an interactive prompt.
|
|
4
|
-
|
|
5
|
-
TODO: Delete this and the text above, and describe your gem
|
|
6
|
-
|
|
7
|
-
## Installation
|
|
8
|
-
|
|
9
|
-
Add this line to your application's Gemfile:
|
|
10
|
-
|
|
11
|
-
```ruby
|
|
12
|
-
gem 'rubocop-digitalhospital'
|
|
13
|
-
```
|
|
14
|
-
|
|
15
|
-
And then execute:
|
|
16
|
-
|
|
17
|
-
$ bundle install
|
|
18
|
-
|
|
19
|
-
Or install it yourself as:
|
|
20
|
-
|
|
21
|
-
$ gem install rubocop-digitalhospital
|
|
22
|
-
|
|
23
|
-
## Usage
|
|
24
|
-
|
|
25
|
-
TODO: Write usage instructions here
|
|
26
|
-
|
|
27
|
-
## Development
|
|
28
|
-
|
|
29
|
-
After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
|
|
30
|
-
|
|
31
|
-
To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
|
|
32
|
-
|
|
33
|
-
## Contributing
|
|
34
|
-
|
|
35
|
-
Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/rubocop-digitalhospital. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/[USERNAME]/rubocop-digitalhospital/blob/master/CODE_OF_CONDUCT.md).
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
## License
|
|
39
|
-
|
|
40
|
-
The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
|
|
41
|
-
|
|
42
|
-
## Code of Conduct
|
|
43
|
-
|
|
44
|
-
Everyone interacting in the Rubocop::Digitalhospital project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/rubocop-digitalhospital/blob/master/CODE_OF_CONDUCT.md).
|
|
1
|
+
# Rubocop::Digitalhospital
|
|
2
|
+
|
|
3
|
+
Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/rubocop/digitalhospital`. To experiment with that code, run `bin/console` for an interactive prompt.
|
|
4
|
+
|
|
5
|
+
TODO: Delete this and the text above, and describe your gem
|
|
6
|
+
|
|
7
|
+
## Installation
|
|
8
|
+
|
|
9
|
+
Add this line to your application's Gemfile:
|
|
10
|
+
|
|
11
|
+
```ruby
|
|
12
|
+
gem 'rubocop-digitalhospital'
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
And then execute:
|
|
16
|
+
|
|
17
|
+
$ bundle install
|
|
18
|
+
|
|
19
|
+
Or install it yourself as:
|
|
20
|
+
|
|
21
|
+
$ gem install rubocop-digitalhospital
|
|
22
|
+
|
|
23
|
+
## Usage
|
|
24
|
+
|
|
25
|
+
TODO: Write usage instructions here
|
|
26
|
+
|
|
27
|
+
## Development
|
|
28
|
+
|
|
29
|
+
After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
|
|
30
|
+
|
|
31
|
+
To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
|
|
32
|
+
|
|
33
|
+
## Contributing
|
|
34
|
+
|
|
35
|
+
Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/rubocop-digitalhospital. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/[USERNAME]/rubocop-digitalhospital/blob/master/CODE_OF_CONDUCT.md).
|
|
36
|
+
|
|
37
|
+
|
|
38
|
+
## License
|
|
39
|
+
|
|
40
|
+
The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
|
|
41
|
+
|
|
42
|
+
## Code of Conduct
|
|
43
|
+
|
|
44
|
+
Everyone interacting in the Rubocop::Digitalhospital project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/rubocop-digitalhospital/blob/master/CODE_OF_CONDUCT.md).
|
data/Rakefile
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
|
-
# frozen_string_literal: true
|
|
2
|
-
|
|
3
|
-
require "bundler/gem_tasks"
|
|
4
|
-
require "rspec/core/rake_task"
|
|
5
|
-
|
|
6
|
-
RSpec::Core::RakeTask.new(:spec)
|
|
7
|
-
|
|
8
|
-
task default: :spec
|
|
1
|
+
# frozen_string_literal: true
|
|
2
|
+
|
|
3
|
+
require "bundler/gem_tasks"
|
|
4
|
+
require "rspec/core/rake_task"
|
|
5
|
+
|
|
6
|
+
RSpec::Core::RakeTask.new(:spec)
|
|
7
|
+
|
|
8
|
+
task default: :spec
|
data/bin/console
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
|
-
#!/usr/bin/env ruby
|
|
2
|
-
|
|
3
|
-
require "bundler/setup"
|
|
4
|
-
require "rubocop/digitalhospital"
|
|
5
|
-
|
|
6
|
-
# You can add fixtures and/or initialization code here to make experimenting
|
|
7
|
-
# with your gem easier. You can also use a different console, if you like.
|
|
8
|
-
|
|
9
|
-
# (If you use this, don't forget to add pry to your Gemfile!)
|
|
10
|
-
# require "pry"
|
|
11
|
-
# Pry.start
|
|
12
|
-
|
|
13
|
-
require "irb"
|
|
14
|
-
IRB.start(__FILE__)
|
|
1
|
+
#!/usr/bin/env ruby
|
|
2
|
+
|
|
3
|
+
require "bundler/setup"
|
|
4
|
+
require "rubocop/digitalhospital"
|
|
5
|
+
|
|
6
|
+
# You can add fixtures and/or initialization code here to make experimenting
|
|
7
|
+
# with your gem easier. You can also use a different console, if you like.
|
|
8
|
+
|
|
9
|
+
# (If you use this, don't forget to add pry to your Gemfile!)
|
|
10
|
+
# require "pry"
|
|
11
|
+
# Pry.start
|
|
12
|
+
|
|
13
|
+
require "irb"
|
|
14
|
+
IRB.start(__FILE__)
|
data/bin/setup
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
|
-
#!/usr/bin/env bash
|
|
2
|
-
set -euo pipefail
|
|
3
|
-
IFS=$'\n\t'
|
|
4
|
-
set -vx
|
|
5
|
-
|
|
6
|
-
bundle install
|
|
7
|
-
|
|
8
|
-
# Do any other automated setup that you need to do here
|
|
1
|
+
#!/usr/bin/env bash
|
|
2
|
+
set -euo pipefail
|
|
3
|
+
IFS=$'\n\t'
|
|
4
|
+
set -vx
|
|
5
|
+
|
|
6
|
+
bundle install
|
|
7
|
+
|
|
8
|
+
# Do any other automated setup that you need to do here
|
|
@@ -1,10 +1,10 @@
|
|
|
1
|
-
# frozen_string_literal: true
|
|
2
|
-
|
|
3
|
-
require "rubocop/digitalhospital/version"
|
|
4
|
-
|
|
5
|
-
module Rubocop
|
|
6
|
-
module Digitalhospital
|
|
7
|
-
class Error < StandardError; end
|
|
8
|
-
# Your code goes here...
|
|
9
|
-
end
|
|
10
|
-
end
|
|
1
|
+
# frozen_string_literal: true
|
|
2
|
+
|
|
3
|
+
require "rubocop/digitalhospital/version"
|
|
4
|
+
|
|
5
|
+
module Rubocop
|
|
6
|
+
module Digitalhospital
|
|
7
|
+
class Error < StandardError; end
|
|
8
|
+
# Your code goes here...
|
|
9
|
+
end
|
|
10
|
+
end
|
data/rubocop-all.yml
CHANGED
|
@@ -1,3 +1,3 @@
|
|
|
1
|
-
AllCops:
|
|
2
|
-
TargetRubyVersion: 2.
|
|
1
|
+
AllCops:
|
|
2
|
+
TargetRubyVersion: 2.7
|
|
3
3
|
NewCops: enable
|
data/rubocop-bundler.yml
CHANGED
|
@@ -1,3 +1,3 @@
|
|
|
1
|
-
# Gems in consecutive lines should be alphabetically sorted
|
|
2
|
-
Bundler/OrderedGems:
|
|
3
|
-
Enabled: false
|
|
1
|
+
# Gems in consecutive lines should be alphabetically sorted
|
|
2
|
+
Bundler/OrderedGems:
|
|
3
|
+
Enabled: false
|
data/rubocop-default.yml
CHANGED
|
@@ -1,18 +1,18 @@
|
|
|
1
|
-
require:
|
|
2
|
-
- rubocop-performance
|
|
3
|
-
- rubocop-rspec
|
|
4
|
-
- rubocop-rails
|
|
5
|
-
|
|
6
|
-
inherit_from:
|
|
7
|
-
- rubocop-all.yml
|
|
8
|
-
- rubocop-bundler.yml
|
|
9
|
-
- rubocop-gemspec.yml
|
|
10
|
-
- rubocop-layout.yml
|
|
11
|
-
- rubocop-lint.yml
|
|
12
|
-
- rubocop-metrics.yml
|
|
13
|
-
- rubocop-migrations.yml
|
|
14
|
-
- rubocop-naming.yml
|
|
15
|
-
- rubocop-performance.yml
|
|
16
|
-
- rubocop-rails.yml
|
|
17
|
-
- rubocop-rspec.yml
|
|
18
|
-
- rubocop-style.yml
|
|
1
|
+
require:
|
|
2
|
+
- rubocop-performance
|
|
3
|
+
- rubocop-rspec
|
|
4
|
+
- rubocop-rails
|
|
5
|
+
|
|
6
|
+
inherit_from:
|
|
7
|
+
- rubocop-all.yml
|
|
8
|
+
- rubocop-bundler.yml
|
|
9
|
+
- rubocop-gemspec.yml
|
|
10
|
+
- rubocop-layout.yml
|
|
11
|
+
- rubocop-lint.yml
|
|
12
|
+
- rubocop-metrics.yml
|
|
13
|
+
- rubocop-migrations.yml
|
|
14
|
+
- rubocop-naming.yml
|
|
15
|
+
- rubocop-performance.yml
|
|
16
|
+
- rubocop-rails.yml
|
|
17
|
+
- rubocop-rspec.yml
|
|
18
|
+
- rubocop-style.yml
|
|
@@ -1,40 +1,41 @@
|
|
|
1
|
-
# frozen_string_literal: true
|
|
2
|
-
|
|
3
|
-
require_relative "lib/rubocop/digitalhospital/version"
|
|
4
|
-
|
|
5
|
-
Gem::Specification.new do |spec|
|
|
6
|
-
spec.name = "rubocop-digitalhospital"
|
|
7
|
-
spec.version = Rubocop::Digitalhospital::VERSION
|
|
8
|
-
spec.authors = ["DigitalHospital"]
|
|
9
|
-
spec.email = ["javi@digitalhospital.com"]
|
|
10
|
-
|
|
11
|
-
spec.summary = "The DigitalHospital rubocop style guide"
|
|
12
|
-
spec.description = "A rubocop style guide"
|
|
13
|
-
spec.homepage = "https://www.digitalhospital.com"
|
|
14
|
-
spec.license = "MIT"
|
|
15
|
-
spec.required_ruby_version = Gem::Requirement.new(">= 2.3.0")
|
|
16
|
-
|
|
17
|
-
# spec.metadata["allowed_push_host"] = "TODO: Set to 'http://mygemserver.com'"
|
|
18
|
-
|
|
19
|
-
spec.metadata["homepage_uri"] = spec.homepage
|
|
20
|
-
spec.metadata["source_code_uri"] = "https://github.com/DigitalHospital/
|
|
21
|
-
spec.metadata["changelog_uri"] = "https://github.com/DigitalHospital/
|
|
22
|
-
|
|
23
|
-
# Specify which files should be added to the gem when it is released.
|
|
24
|
-
# The `git ls-files -z` loads the files in the RubyGem that have been added into git.
|
|
25
|
-
spec.files = Dir.chdir(File.expand_path(__dir__)) do
|
|
26
|
-
`git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
|
|
27
|
-
end
|
|
28
|
-
|
|
29
|
-
spec.
|
|
30
|
-
spec.
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
spec.add_dependency "rubocop
|
|
34
|
-
spec.add_dependency "rubocop-
|
|
35
|
-
spec.add_dependency "rubocop-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
spec.add_development_dependency "
|
|
39
|
-
spec.add_development_dependency "
|
|
40
|
-
|
|
1
|
+
# frozen_string_literal: true
|
|
2
|
+
|
|
3
|
+
require_relative "lib/rubocop/digitalhospital/version"
|
|
4
|
+
|
|
5
|
+
Gem::Specification.new do |spec|
|
|
6
|
+
spec.name = "rubocop-digitalhospital"
|
|
7
|
+
spec.version = Rubocop::Digitalhospital::VERSION
|
|
8
|
+
spec.authors = ["DigitalHospital"]
|
|
9
|
+
spec.email = ["javi@digitalhospital.com"]
|
|
10
|
+
|
|
11
|
+
spec.summary = "The DigitalHospital rubocop style guide"
|
|
12
|
+
spec.description = "A rubocop style guide"
|
|
13
|
+
spec.homepage = "https://www.digitalhospital.com"
|
|
14
|
+
spec.license = "MIT"
|
|
15
|
+
spec.required_ruby_version = Gem::Requirement.new(">= 2.3.0")
|
|
16
|
+
|
|
17
|
+
# spec.metadata["allowed_push_host"] = "TODO: Set to 'http://mygemserver.com'"
|
|
18
|
+
|
|
19
|
+
spec.metadata["homepage_uri"] = spec.homepage
|
|
20
|
+
spec.metadata["source_code_uri"] = "https://github.com/DigitalHospital/rubocop-digitalhospital"
|
|
21
|
+
spec.metadata["changelog_uri"] = "https://github.com/DigitalHospital/rubocop-digitalhospital/issues"
|
|
22
|
+
|
|
23
|
+
# Specify which files should be added to the gem when it is released.
|
|
24
|
+
# The `git ls-files -z` loads the files in the RubyGem that have been added into git.
|
|
25
|
+
spec.files = Dir.chdir(File.expand_path(__dir__)) do
|
|
26
|
+
`git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
|
|
27
|
+
end
|
|
28
|
+
|
|
29
|
+
spec.bindir = "exe"
|
|
30
|
+
spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
|
|
31
|
+
spec.require_paths = ["lib"]
|
|
32
|
+
|
|
33
|
+
spec.add_dependency "rubocop"
|
|
34
|
+
spec.add_dependency "rubocop-performance"
|
|
35
|
+
spec.add_dependency "rubocop-rails"
|
|
36
|
+
spec.add_dependency "rubocop-rspec"
|
|
37
|
+
|
|
38
|
+
spec.add_development_dependency "bundler"
|
|
39
|
+
spec.add_development_dependency "rake"
|
|
40
|
+
spec.add_development_dependency "rspec"
|
|
41
|
+
end
|
data/rubocop-gemspec.yml
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
|
-
# Dependencies in the gemspec should be alphabetically sorted
|
|
2
|
-
# Configuration parameters: Include, TreatCommentsAsGroupSeparators.
|
|
3
|
-
Gemspec/OrderedDependencies:
|
|
4
|
-
Include:
|
|
5
|
-
- '**/*.gemspec'
|
|
1
|
+
# Dependencies in the gemspec should be alphabetically sorted
|
|
2
|
+
# Configuration parameters: Include, TreatCommentsAsGroupSeparators.
|
|
3
|
+
Gemspec/OrderedDependencies:
|
|
4
|
+
Include:
|
|
5
|
+
- '**/*.gemspec'
|
data/rubocop-layout.yml
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
|
-
# Limit lines to 120 characters.
|
|
2
|
-
Layout/LineLength:
|
|
3
|
-
Enabled: true
|
|
4
|
-
Max: 120
|
|
1
|
+
# Limit lines to 120 characters.
|
|
2
|
+
Layout/LineLength:
|
|
3
|
+
Enabled: true
|
|
4
|
+
Max: 120
|
|
5
5
|
IgnoredPatterns: ['\s#\srubocop']
|
data/rubocop-lint.yml
CHANGED
|
File without changes
|
data/rubocop-metrics.yml
CHANGED
|
@@ -1,42 +1,42 @@
|
|
|
1
|
-
# A calculated magnitude based on number of assignments,
|
|
2
|
-
# branches, and conditions.
|
|
3
|
-
Metrics/AbcSize:
|
|
4
|
-
Enabled: true
|
|
5
|
-
Max: 54.28
|
|
6
|
-
|
|
7
|
-
# This cop checks if the length of a block exceeds some maximum value.
|
|
8
|
-
Metrics/BlockLength:
|
|
9
|
-
Enabled: false
|
|
10
|
-
|
|
11
|
-
# Avoid excessive block nesting.
|
|
12
|
-
Metrics/BlockNesting:
|
|
13
|
-
Enabled: true
|
|
14
|
-
Max: 4
|
|
15
|
-
|
|
16
|
-
# Avoid classes longer than 100 lines of code.
|
|
17
|
-
Metrics/ClassLength:
|
|
18
|
-
Enabled: false
|
|
19
|
-
|
|
20
|
-
# A complexity metric that is strongly correlated to the number
|
|
21
|
-
# of test cases needed to validate a method.
|
|
22
|
-
Metrics/CyclomaticComplexity:
|
|
23
|
-
Enabled: true
|
|
24
|
-
Max: 13
|
|
25
|
-
|
|
26
|
-
# Avoid methods longer than 10 lines of code.
|
|
27
|
-
Metrics/MethodLength:
|
|
28
|
-
Enabled: false
|
|
29
|
-
|
|
30
|
-
# Avoid modules longer than 100 lines of code.
|
|
31
|
-
Metrics/ModuleLength:
|
|
32
|
-
Enabled: false
|
|
33
|
-
|
|
34
|
-
# Avoid parameter lists longer than three or four parameters.
|
|
35
|
-
Metrics/ParameterLists:
|
|
36
|
-
Enabled: true
|
|
37
|
-
Max: 8
|
|
38
|
-
|
|
39
|
-
# A complexity metric geared towards measuring complexity for a human reader.
|
|
40
|
-
Metrics/PerceivedComplexity:
|
|
41
|
-
Enabled: true
|
|
42
|
-
Max: 14
|
|
1
|
+
# A calculated magnitude based on number of assignments,
|
|
2
|
+
# branches, and conditions.
|
|
3
|
+
Metrics/AbcSize:
|
|
4
|
+
Enabled: true
|
|
5
|
+
Max: 54.28
|
|
6
|
+
|
|
7
|
+
# This cop checks if the length of a block exceeds some maximum value.
|
|
8
|
+
Metrics/BlockLength:
|
|
9
|
+
Enabled: false
|
|
10
|
+
|
|
11
|
+
# Avoid excessive block nesting.
|
|
12
|
+
Metrics/BlockNesting:
|
|
13
|
+
Enabled: true
|
|
14
|
+
Max: 4
|
|
15
|
+
|
|
16
|
+
# Avoid classes longer than 100 lines of code.
|
|
17
|
+
Metrics/ClassLength:
|
|
18
|
+
Enabled: false
|
|
19
|
+
|
|
20
|
+
# A complexity metric that is strongly correlated to the number
|
|
21
|
+
# of test cases needed to validate a method.
|
|
22
|
+
Metrics/CyclomaticComplexity:
|
|
23
|
+
Enabled: true
|
|
24
|
+
Max: 13
|
|
25
|
+
|
|
26
|
+
# Avoid methods longer than 10 lines of code.
|
|
27
|
+
Metrics/MethodLength:
|
|
28
|
+
Enabled: false
|
|
29
|
+
|
|
30
|
+
# Avoid modules longer than 100 lines of code.
|
|
31
|
+
Metrics/ModuleLength:
|
|
32
|
+
Enabled: false
|
|
33
|
+
|
|
34
|
+
# Avoid parameter lists longer than three or four parameters.
|
|
35
|
+
Metrics/ParameterLists:
|
|
36
|
+
Enabled: true
|
|
37
|
+
Max: 8
|
|
38
|
+
|
|
39
|
+
# A complexity metric geared towards measuring complexity for a human reader.
|
|
40
|
+
Metrics/PerceivedComplexity:
|
|
41
|
+
Enabled: true
|
|
42
|
+
Max: 14
|
data/rubocop-migrations.yml
CHANGED
|
@@ -1,19 +1,19 @@
|
|
|
1
|
-
# Checks for methods that may lead to batch type issues on a table that's been
|
|
2
|
-
# explicitly denied because of its size.
|
|
3
|
-
#
|
|
4
|
-
# Even though these methods perform functions to avoid
|
|
5
|
-
# downtime, using it with tables with millions of rows still causes a
|
|
6
|
-
# significant delay in the deploy process and is best avoided.
|
|
7
|
-
#
|
|
8
|
-
# See https://gitlab.com/gitlab-com/infrastructure/issues/1602 for more
|
|
9
|
-
# information.
|
|
10
|
-
# The default can be changed as follows:
|
|
11
|
-
# Migration/UpdateLargeTable:
|
|
12
|
-
# DeniedTables:
|
|
13
|
-
# - :usage_data
|
|
14
|
-
# - :version_checks
|
|
15
|
-
# DeniedMethods:
|
|
16
|
-
# - :add_column_with_default
|
|
17
|
-
# - :change_column_type_concurrently
|
|
18
|
-
# - :rename_column_concurrently
|
|
19
|
-
# - :update_column_in_batches
|
|
1
|
+
# Checks for methods that may lead to batch type issues on a table that's been
|
|
2
|
+
# explicitly denied because of its size.
|
|
3
|
+
#
|
|
4
|
+
# Even though these methods perform functions to avoid
|
|
5
|
+
# downtime, using it with tables with millions of rows still causes a
|
|
6
|
+
# significant delay in the deploy process and is best avoided.
|
|
7
|
+
#
|
|
8
|
+
# See https://gitlab.com/gitlab-com/infrastructure/issues/1602 for more
|
|
9
|
+
# information.
|
|
10
|
+
# The default can be changed as follows:
|
|
11
|
+
# Migration/UpdateLargeTable:
|
|
12
|
+
# DeniedTables:
|
|
13
|
+
# - :usage_data
|
|
14
|
+
# - :version_checks
|
|
15
|
+
# DeniedMethods:
|
|
16
|
+
# - :add_column_with_default
|
|
17
|
+
# - :change_column_type_concurrently
|
|
18
|
+
# - :rename_column_concurrently
|
|
19
|
+
# - :update_column_in_batches
|
data/rubocop-naming.yml
CHANGED
|
File without changes
|
data/rubocop-performance.yml
CHANGED
|
File without changes
|
data/rubocop-rails.yml
CHANGED
|
File without changes
|
data/rubocop-rspec.yml
CHANGED
|
File without changes
|
data/rubocop-style.yml
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
|
-
# Document classes and non-namespace modules.
|
|
2
|
-
Style/Documentation:
|
|
3
|
-
Enabled: false
|
|
4
|
-
|
|
5
|
-
# Check quotes usage according to lint rule below.
|
|
6
|
-
Style/StringLiterals:
|
|
7
|
-
Enabled: true
|
|
1
|
+
# Document classes and non-namespace modules.
|
|
2
|
+
Style/Documentation:
|
|
3
|
+
Enabled: false
|
|
4
|
+
|
|
5
|
+
# Check quotes usage according to lint rule below.
|
|
6
|
+
Style/StringLiterals:
|
|
7
|
+
Enabled: true
|
|
8
8
|
EnforcedStyle: double_quotes
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: rubocop-digitalhospital
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.
|
|
4
|
+
version: 0.3.0
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- DigitalHospital
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: exe
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date:
|
|
11
|
+
date: 2022-12-14 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: rubocop
|
|
@@ -150,8 +150,8 @@ licenses:
|
|
|
150
150
|
- MIT
|
|
151
151
|
metadata:
|
|
152
152
|
homepage_uri: https://www.digitalhospital.com
|
|
153
|
-
source_code_uri: https://github.com/DigitalHospital/
|
|
154
|
-
changelog_uri: https://github.com/DigitalHospital/
|
|
153
|
+
source_code_uri: https://github.com/DigitalHospital/rubocop-digitalhospital
|
|
154
|
+
changelog_uri: https://github.com/DigitalHospital/rubocop-digitalhospital/issues
|
|
155
155
|
post_install_message:
|
|
156
156
|
rdoc_options: []
|
|
157
157
|
require_paths:
|
|
@@ -167,7 +167,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
|
167
167
|
- !ruby/object:Gem::Version
|
|
168
168
|
version: '0'
|
|
169
169
|
requirements: []
|
|
170
|
-
rubygems_version: 3.
|
|
170
|
+
rubygems_version: 3.1.6
|
|
171
171
|
signing_key:
|
|
172
172
|
specification_version: 4
|
|
173
173
|
summary: The DigitalHospital rubocop style guide
|