enola-guides 0.3.0 → 0.3.1
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 +4 -4
- data/CHANGELOG.md +6 -0
- data/lib/enola-guides.rb +1 -1
- data/recipes/README.md +19 -13
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: f8f7f20100ffdeea1ae928ad9e76186848aeba81caed9491993e09cfc5bc7461
|
|
4
|
+
data.tar.gz: dcbacd0bba3cf8ee9883b1590a8cd969d1c01150d4549789c1869920dad8de9e
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: f3de1b04dfb1ec8c76f2686d4730052a0f38175721ea288294a09e1f4c2be4fa154d9622748405204b086857bdc5de3969675b49f729b0a5f229f5b8dc5ebebb
|
|
7
|
+
data.tar.gz: 49e2f753fa478c657683dbe69b729774dc94129a8ba8bf3c6614469b7576e0752857daa266f993006098e8a3e36eeeada89377412548d122c83f9d4fa41d1a01
|
data/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.3.1 (2026-08-23)
|
|
4
|
+
|
|
5
|
+
The recipes README says where the catalogue ships: built into munola,
|
|
6
|
+
written by `munola init`; the upstream channels carry upstream's built-ins
|
|
7
|
+
only.
|
|
8
|
+
|
|
3
9
|
## 0.3.0 (2026-08-23)
|
|
4
10
|
|
|
5
11
|
The recipe catalogue munola binds: `data-ownership`, `api-boundaries`,
|
data/lib/enola-guides.rb
CHANGED
data/recipes/README.md
CHANGED
|
@@ -40,20 +40,26 @@ breach. Start with ratchet.
|
|
|
40
40
|
|
|
41
41
|
## The recipes
|
|
42
42
|
|
|
43
|
-
The catalogue munola
|
|
44
|
-
|
|
45
|
-
|
|
43
|
+
The catalogue munola ships built in: `munola init` writes these recipes
|
|
44
|
+
into a project's `enola/recipes/` and binds those whose roles resolve,
|
|
45
|
+
and the munola binary embeds the parameter-free ones, generated from
|
|
46
|
+
these files at release. The `enola` and `enola-rb` gems carry upstream's
|
|
47
|
+
own built-ins only (`rails-conventions`, `rails-strict`, `vanilla-rails`
|
|
48
|
+
and the six arrangements); a team on those channels copies a file from
|
|
49
|
+
here by hand. Each law is
|
|
50
|
+
an existing enola form; each recipe is here because its laws held on a real
|
|
51
|
+
Rails monolith at a number a team can act on, given beside it.
|
|
46
52
|
|
|
47
|
-
| Recipe | States | Held at |
|
|
48
|
-
|
|
49
|
-
| `rails-conventions` (upstream) | jobs, models, serializers and components never render; policies and mailers never enqueue; request API stays in controllers | five of seven laws with zero exceptions, three advisory at 134 crossings |
|
|
50
|
-
| `rails-strict` (upstream) | the above plus no cycles among the Rails roles and independent concerns | 0 of 127 concerns breach |
|
|
51
|
-
| `vanilla-rails` (upstream) | the directories the vanilla arrangement leaves empty stay empty | an arrangement a team chooses |
|
|
52
|
-
| `ember-conventions.yaml` | nine Ember conventions selected by what the code carries | the neutral eight hold; the house ones stay out |
|
|
53
|
-
| `data-ownership.yaml` | readers read the store only | advisory; bind your query objects |
|
|
54
|
-
| `api-boundaries.yaml` | the public API is reached only by controllers; a mutating action reaches a policy | 736 unauthorized mutations reported, advisory |
|
|
55
|
-
| `background-work.yaml` | maintenance tasks live in their namespace and never reach controllers | 0 of 3,250 task call edges reach a controller |
|
|
56
|
-
| `tenant-foreign-key.yaml` | a table carrying the tenant column carries the foreign key | 3,720 declared, 0 new |
|
|
53
|
+
| Recipe | States | Held at |
|
|
54
|
+
|---|---|---|
|
|
55
|
+
| `rails-conventions` (upstream) | jobs, models, serializers and components never render; policies and mailers never enqueue; request API stays in controllers | five of seven laws with zero exceptions, three advisory at 134 crossings |
|
|
56
|
+
| `rails-strict` (upstream) | the above plus no cycles among the Rails roles and independent concerns | 0 of 127 concerns breach |
|
|
57
|
+
| `vanilla-rails` (upstream) | the directories the vanilla arrangement leaves empty stay empty | an arrangement a team chooses |
|
|
58
|
+
| `ember-conventions.yaml` | nine Ember conventions selected by what the code carries | the neutral eight hold; the house ones stay out |
|
|
59
|
+
| `data-ownership.yaml` | readers read the store only | advisory; bind your query objects |
|
|
60
|
+
| `api-boundaries.yaml` | the public API is reached only by controllers; a mutating action reaches a policy | 736 unauthorized mutations reported, advisory |
|
|
61
|
+
| `background-work.yaml` | maintenance tasks live in their namespace and never reach controllers | 0 of 3,250 task call edges reach a controller |
|
|
62
|
+
| `tenant-foreign-key.yaml` | a table carrying the tenant column carries the foreign key | 3,720 declared, 0 new |
|
|
57
63
|
|
|
58
64
|
Two data-ownership laws, one owner per table and storage stays home, are
|
|
59
65
|
declarations rather than recipe rules for now: they live as worked examples
|