rails_routes_analyzer 1.0.1 → 1.0.3
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +5 -0
- data/lib/rails_routes_analyzer/version.rb +1 -1
- data/rails_routes_analyzer.gemspec +1 -1
- metadata +2 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 3f5165b7944953c43c7a59c29489bf7d8c018358
|
|
4
|
+
data.tar.gz: 1a3c06a1cf4234ab2efc65023b77a3af9dd9c657
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: ffe03cbea224d6fa0dae6fe97058b0095a45e1cd6aa9ad7ad8c4fb9d15545158592cd36bb411a55994a298c00c2acf9e48f1499b3fbf3395b807b1a0dee6aa92
|
|
7
|
+
data.tar.gz: c36810e886f072f7ed8f6674e1f08c0c97e481441d698592b65f28e149e8cb90503d10da882d8415c53400ef1c55e78023808e1e8e4c7e5d299d445b5ccd02ec
|
data/README.md
CHANGED
|
@@ -28,6 +28,11 @@ For complex cases where for example a routes are created in a loop for multiple
|
|
|
28
28
|
|
|
29
29
|
``` sh
|
|
30
30
|
rake routes:annotate_dead [ANNOTATE=path/to/routes.rb]
|
|
31
|
+
|
|
32
|
+
# Best used like this:
|
|
33
|
+
rake routes:annotate_dead > config/routest.rb.new
|
|
34
|
+
mv config/routes.rb.new config/routes.rb
|
|
35
|
+
# And then update the file as requested in any SUGGESTION comments
|
|
31
36
|
```
|
|
32
37
|
|
|
33
38
|
Will output an annotated version of config/routes.rb or any other routes file as provided in the ANNOTATE parameter.
|
|
@@ -6,7 +6,7 @@ require 'rails_routes_analyzer/version'
|
|
|
6
6
|
Gem::Specification.new do |spec|
|
|
7
7
|
spec.name = "rails_routes_analyzer"
|
|
8
8
|
spec.version = RailsRoutesAnalyzer::VERSION
|
|
9
|
-
spec.authors = ["Tarmo Tänav"]
|
|
9
|
+
spec.authors = ["Bear Metal OÜ", "Tarmo Tänav"]
|
|
10
10
|
spec.email = ["tarmo@bearmetal.eu"]
|
|
11
11
|
|
|
12
12
|
spec.summary = %q{Helps clean up rails routes}
|