@reventlessdev/trait-address-geocoding 1.0.0-alpha.1 → 1.0.0-alpha.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reventlessdev/trait-address-geocoding",
-  "version": "1.0.0-alpha.1",
+  "version": "1.0.0-alpha.3",
   "description": "Address-geocoding domain trait: rules, host contract, conformance suite and emitter for grafting geocoding onto an aggregate",
   "license": "Apache-2.0",
   "files": [
@@ -13,10 +13,10 @@
   "dependencies": {
     "sury": "11.0.0-rc.2",
     "sury-ppx": "11.0.0-rc.2",
-    "@reventlessdev/reventless-infra": "3.0.0-alpha.153",
-    "@reventlessdev/reventless-gwt": "1.0.0-alpha.199",
-    "@reventlessdev/reventless-ppx": "1.0.0-alpha.75",
-    "@reventlessdev/reventless-spec": "3.0.0-alpha.125"
+    "@reventlessdev/reventless-gwt": "1.0.0-alpha.201",
+    "@reventlessdev/reventless-infra": "3.0.0-alpha.155",
+    "@reventlessdev/reventless-ppx": "1.0.0-alpha.76",
+    "@reventlessdev/reventless-spec": "3.0.0-alpha.127"
   },
   "devDependencies": {
     "rescript": "12.3.0"

package/src/AddressGeocoding.res

@@ -102,11 +102,11 @@ The two commands a caller changes the address through, as constructors a host
 splices into its own command type.
 
 These are public, and that is what kept them out of the trait until now. Both
-are legal only while the entity is in some state the HOST names, and a
-`@transition` cannot be attached to a constructor a host did not declare — it
-lowers to a dict on the parent union, and a spread splices members. So the pair
-stayed hand-written in every host, which is the whole of what a spreading host
-still had to transcribe.
+are legal only while the entity is in some state the HOST names, and the
+attribute that used to declare that could not be attached to a constructor a
+host did not declare — it lowered to a dict on the parent union, and a spread
+splices members. So the pair stayed hand-written in every host, which is the
+whole of what a spreading host still had to transcribe.
 
 `commandTransition` is what freed them: the host answers for them in an
 exhaustive switch, in its own lifecycle vocabulary, and the compiler will not let

package/src/AddressGeocoding_Scaffold.res

@@ -24,8 +24,8 @@ and a host that needs it says so.
 
 **What it does not do.** It never writes the host's policy. Which states an
 address may be changed in, who may change it, what a host's own commands refuse
-— those are `@transition` and `@authorize` over the host's own lifecycle, which
-a trait cannot know. They are config when the host supplies them and absent
+— those are `commandTransition` and `@authorize` over the host's own lifecycle,
+which a trait cannot know. They are config when the host supplies them and absent
 when it does not.
 */
 
@@ -358,8 +358,8 @@ let conformanceBinding = (c: config): string => {
 // host choice: a report must be legal in every state, or an answer landing after
 // the entity moved on parks a TODO row forever. The two public commands are the
 // host's call, so they are printed as a marked hole. That split is the same one
-// the whole scaffold runs on, and it is why `@transition` could not serve here:
-// an attribute cannot be attached to a constructor the host did not declare.
+// the whole scaffold runs on, and it is why an attribute could not serve here:
+// one cannot be attached to a constructor the host did not declare.
 let transitionArms = (c: config): array<string> => {
   let n = namesOf(c)
   [