modularization_statistics 1.39.0 → 1.41.0
Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 98507b7d02a58d6a68c9ba40d9962abf6369dc68959d7a95f6d3a49384f902f4
|
|
4
|
+
data.tar.gz: 5d12d05d262833e8b1534a6b38f8162b2a3c4bd57d584ceb260a5c8d6c99ab0a
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 41ddf6056104fcc66a39f44bf50e4783cd69fe70aa88414bd5459c365bd0285439d3bfe8651b4ab3059f849759b8e37afe5502fdf907654798640a6c9cade2ff
|
|
7
|
+
data.tar.gz: f72b2b1c78f6bddbeac30bfd074b3a8b2bcc0b18e20ad9fc0b311e32ee4514aabc95683d12642b0287cbea41457e46f7468fa849f6b198ff06703f69f768534a
|
|
@@ -27,7 +27,7 @@ module ModularizationStatistics
|
|
|
27
27
|
#
|
|
28
28
|
# This is temporarily in place until we migrate off of `package_protections` in favor of `rubocop-packs`.
|
|
29
29
|
# At that point, we want to delete this branch and instead it we'd probably have two separate branches.
|
|
30
|
-
# One branch would look at `enforce_x` and `metadata.
|
|
30
|
+
# One branch would look at `enforce_x` and `metadata.enforce_x_strictly`.
|
|
31
31
|
# The other branch would look at `.pack_rubocop.yml`.
|
|
32
32
|
# Later on, we could generalize this so that it automatically incorporates new cops from `rubocop-packs`,
|
|
33
33
|
# or even new packwerk plugins.
|
|
@@ -66,7 +66,7 @@ module ModularizationStatistics
|
|
|
66
66
|
end
|
|
67
67
|
def self.should_count_package?(package, protection, violation_behavior)
|
|
68
68
|
if protection.identifier == 'prevent_this_package_from_violating_its_stated_dependencies'
|
|
69
|
-
strict_mode = package.metadata['
|
|
69
|
+
strict_mode = package.metadata['enforce_dependencies_strictly']
|
|
70
70
|
enabled = package.enforces_dependencies?
|
|
71
71
|
|
|
72
72
|
case violation_behavior
|
|
@@ -80,7 +80,7 @@ module ModularizationStatistics
|
|
|
80
80
|
T.absurd(violation_behavior)
|
|
81
81
|
end
|
|
82
82
|
elsif protection.identifier == 'prevent_other_packages_from_using_this_packages_internals'
|
|
83
|
-
strict_mode = package.metadata['
|
|
83
|
+
strict_mode = package.metadata['enforce_privacy_strictly']
|
|
84
84
|
enabled = package.enforces_privacy?
|
|
85
85
|
|
|
86
86
|
case violation_behavior
|
|
@@ -119,10 +119,10 @@ module ModularizationStatistics
|
|
|
119
119
|
# in which case we wouldn't get the right metrics with this approach. However, we can also accept
|
|
120
120
|
# that as a current limitation.
|
|
121
121
|
cop_map = {
|
|
122
|
-
'PackageProtections/TypedPublicApi' => 'Packs/
|
|
123
|
-
'PackageProtections/NamespacedUnderPackageName' => 'Packs/
|
|
122
|
+
'PackageProtections/TypedPublicApi' => 'Packs/TypedPublicApis',
|
|
123
|
+
'PackageProtections/NamespacedUnderPackageName' => 'Packs/RootNamespaceIsPackName',
|
|
124
124
|
'PackageProtections/OnlyClassMethods' => 'Packs/ClassMethodsAsPublicApis',
|
|
125
|
-
'PackageProtections/RequireDocumentedPublicApis' => 'Packs/
|
|
125
|
+
'PackageProtections/RequireDocumentedPublicApis' => 'Packs/DocumentedPublicApis',
|
|
126
126
|
}
|
|
127
127
|
# We want to use the cop names from `rubocop-packs`. Eventually, we'll just literate over these
|
|
128
128
|
# cop names directly, or ask `rubocop-packs` for the list of cops to care about.
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: modularization_statistics
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 1.
|
|
4
|
+
version: 1.41.0
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Gusto Engineers
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2022-11-
|
|
11
|
+
date: 2022-11-14 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: code_teams
|