@drawbridge/drawbridge-utils 0.0.115 → 0.0.116

package/dist/connections/index.cjs

@@ -477,7 +477,13 @@ var attentive_default2 = {
   // connection DOCUMENT carries its own `errors` array and is spread OVER the
   // resolved manifest downstream, so a top-level one would never render.
   content: {
-    confirm: "Disconnecting revokes Drawbridge's access to your Attentive account. Your subscribers stay in both Attentive and Drawbridge \u2014 neither list is deleted.",
+    // SAYS WHAT ACTUALLY HAPPENS. This used to promise that disconnecting
+    // revokes Drawbridge's access, and it cannot: Attentive documents no
+    // revocation endpoint, and their authentication page states an access
+    // token "does not expire". So the grant survives a disconnect forever
+    // unless the merchant removes the integration at Attentive, and the copy
+    // has to say so rather than let them believe otherwise.
+    confirm: "Disconnecting removes Drawbridge's stored Attentive token. Attentive does not offer a way for us to revoke it, so remove the Drawbridge integration in Attentive as well if you want its access fully withdrawn. Your subscribers stay in both Attentive and Drawbridge \u2014 neither list is deleted.",
     description: [
       "Attentive is where your SMS marketing lives, and this connection is becoming the way your Drawbridge contacts sync into an Attentive segment.",
       "You authorize Drawbridge from inside Attentive and can revoke that access there at any time. Drawbridge never sees or stores your Attentive password.",
@@ -518,8 +524,15 @@ var attentive_default2 = {
       // account-identity endpoint to enrich them with — Klaviyo's connect
       // reads the account name back; this has nothing cited to read. The
       // callback stores the tokens and skips enrichment on `unimplemented`.
-      connect: {},
-      disconnect: {},
+      // FALSE, NOT {}. `{}` means "supported, implemented in the repo with the
+      // dependencies", and nothing anywhere implements either of these —
+      // there is nothing for them to do. The exchange already yields the
+      // tokens and Attentive documents no account-identity endpoint to
+      // enrich them with, so connect has nothing to add; and they document
+      // no revocation endpoint at all, so disconnect has nothing to call.
+      // Recorded as a decision rather than left as an unkept promise.
+      connect: false,
+      disconnect: false,
       probe: false,
       scopes: false,
       // THE ONE THING WRAPPED, and it is about the response rather than the
@@ -2189,10 +2202,14 @@ var mailchimp_default2 = {
   // contacts.sync are the first to flip.
   hooks: {
     auth: {
-      // Implemented outside this package: storing a typed key needs no vendor
-      // call, so the api's own form handler does it.
-      connect: {},
-      disconnect: {},
+      // FALSE, NOT {}. `{}` promises an implementation living in the repo that
+      // holds the dependencies, and there is no implementation anywhere
+      // because there is nothing to implement: storing and clearing a typed
+      // key needs no vendor call, and the api's own form handler does it.
+      // Declaring `{}` made the coverage check chase a body that does not
+      // exist, and made a caller wait on an answer that never comes.
+      connect: false,
+      disconnect: false,
       probe: false,
       scopes: false,
       // Keys today. When Mailchimp's OAuth lands this becomes a wrapper that
@@ -2413,10 +2430,29 @@ var shopify_default2 = {
       // re-registers rather than answering "is this token still good", and
       // scope drift is its own hook because a token can be perfectly valid
       // while the grant is too narrow.
-      connect: {},
-      disconnect: {},
+      //
+      // connect and disconnect are FALSE rather than `{}`: there is nothing to
+      // call on either side. The install already hands the callback everything
+      // it stores, and a Shopify grant is withdrawn by UNINSTALLING the app in
+      // Shopify admin — which Drawbridge learns about from the app_uninstalled
+      // webhook rather than by asking. `{}` claimed a body implemented
+      // elsewhere; none exists, and none could.
+      connect: false,
+      disconnect: false,
       probe: false,
-      scopes: {},
+      // WHETHER THE GRANT IS STILL WIDE ENOUGH. A token can be perfectly valid
+      // and still too narrow — a deploy that adds a scope leaves every existing
+      // install short of it, and no webhook fires to say so.
+      //
+      // The comparison is the vendor's, so it belongs here. Reading WHICH
+      // scopes a store granted is not: that lives in the `shop` collection and
+      // needs a controller, which is precisely what a hook in a published
+      // package must not be handed. The caller reads the grant and passes the
+      // string; this answers what is missing from it.
+      //
+      // `shopify` is injected for the same reason it is everywhere else — this
+      // package cannot import @drawbridge/shopify, which depends on it.
+      scopes: ({ scope, shopify }) => scope ? shopify.oauth.missingScopes(scope) : null,
       // Shopify's install grant is exchanged inside its own app flow, not
       // through the shared OAuth runner.
       token: false
@@ -2879,10 +2915,12 @@ var webhook_default = {
   // connect generates a secret rather than proving a credential.
   hooks: {
     auth: {
-      // Minting and clearing a secret needs no vendor call, so the api's own
-      // handler does both.
-      connect: {},
-      disconnect: {},
+      // FALSE, NOT {}. There is no vendor here at all — connecting mints a
+      // secret and disconnecting clears it, both done by the api's own
+      // handler. `{}` would promise a body implemented elsewhere, and none
+      // exists or could.
+      connect: false,
+      disconnect: false,
       probe: false,
       scopes: false,
       // Nothing to mint. Connecting generates a secret; there is no vendor.

package/dist/connections/index.d.cts

@@ -603,7 +603,13 @@ var attentive = {
 	// connection DOCUMENT carries its own `errors` array and is spread OVER the
 	// resolved manifest downstream, so a top-level one would never render.
 	content : {
-		confirm : 'Disconnecting revokes Drawbridge\'s access to your Attentive account. Your subscribers stay in both Attentive and Drawbridge — neither list is deleted.',
+		// SAYS WHAT ACTUALLY HAPPENS. This used to promise that disconnecting
+		// revokes Drawbridge's access, and it cannot: Attentive documents no
+		// revocation endpoint, and their authentication page states an access
+		// token "does not expire". So the grant survives a disconnect forever
+		// unless the merchant removes the integration at Attentive, and the copy
+		// has to say so rather than let them believe otherwise.
+		confirm : 'Disconnecting removes Drawbridge\'s stored Attentive token. Attentive does not offer a way for us to revoke it, so remove the Drawbridge integration in Attentive as well if you want its access fully withdrawn. Your subscribers stay in both Attentive and Drawbridge — neither list is deleted.',
 		description : [
 			'Attentive is where your SMS marketing lives, and this connection is becoming the way your Drawbridge contacts sync into an Attentive segment.',
 			'You authorize Drawbridge from inside Attentive and can revoke that access there at any time. Drawbridge never sees or stores your Attentive password.',
@@ -645,8 +651,15 @@ var attentive = {
 			// account-identity endpoint to enrich them with — Klaviyo's connect
 			// reads the account name back; this has nothing cited to read. The
 			// callback stores the tokens and skips enrichment on `unimplemented`.
-			connect : {},
-			disconnect : {},
+			// FALSE, NOT {}. `{}` means "supported, implemented in the repo with the
+			// dependencies", and nothing anywhere implements either of these —
+			// there is nothing for them to do. The exchange already yields the
+			// tokens and Attentive documents no account-identity endpoint to
+			// enrich them with, so connect has nothing to add; and they document
+			// no revocation endpoint at all, so disconnect has nothing to call.
+			// Recorded as a decision rather than left as an unkept promise.
+			connect : false,
+			disconnect : false,
 			probe : false,
 			scopes : false,
 			// THE ONE THING WRAPPED, and it is about the response rather than the
@@ -2018,10 +2031,14 @@ var mailchimp = {
 	hooks : {
 
 		auth : {
-			// Implemented outside this package: storing a typed key needs no vendor
-			// call, so the api's own form handler does it.
-			connect : {},
-			disconnect : {},
+			// FALSE, NOT {}. `{}` promises an implementation living in the repo that
+			// holds the dependencies, and there is no implementation anywhere
+			// because there is nothing to implement: storing and clearing a typed
+			// key needs no vendor call, and the api's own form handler does it.
+			// Declaring `{}` made the coverage check chase a body that does not
+			// exist, and made a caller wait on an answer that never comes.
+			connect : false,
+			disconnect : false,
 			probe : false,
 			scopes : false,
 			// Keys today. When Mailchimp's OAuth lands this becomes a wrapper that
@@ -2322,10 +2339,30 @@ var shopify = {
 			// re-registers rather than answering "is this token still good", and
 			// scope drift is its own hook because a token can be perfectly valid
 			// while the grant is too narrow.
-			connect : {},
-			disconnect : {},
+			//
+			// connect and disconnect are FALSE rather than `{}`: there is nothing to
+			// call on either side. The install already hands the callback everything
+			// it stores, and a Shopify grant is withdrawn by UNINSTALLING the app in
+			// Shopify admin — which Drawbridge learns about from the app_uninstalled
+			// webhook rather than by asking. `{}` claimed a body implemented
+			// elsewhere; none exists, and none could.
+			connect : false,
+			disconnect : false,
 			probe : false,
-			scopes : {},
+
+			// WHETHER THE GRANT IS STILL WIDE ENOUGH. A token can be perfectly valid
+			// and still too narrow — a deploy that adds a scope leaves every existing
+			// install short of it, and no webhook fires to say so.
+			//
+			// The comparison is the vendor's, so it belongs here. Reading WHICH
+			// scopes a store granted is not: that lives in the `shop` collection and
+			// needs a controller, which is precisely what a hook in a published
+			// package must not be handed. The caller reads the grant and passes the
+			// string; this answers what is missing from it.
+			//
+			// `shopify` is injected for the same reason it is everywhere else — this
+			// package cannot import @drawbridge/shopify, which depends on it.
+			scopes : ({ scope, shopify }) => ( scope ? shopify.oauth.missingScopes( scope ) : null ),
 			// Shopify's install grant is exchanged inside its own app flow, not
 			// through the shared OAuth runner.
 			token : false
@@ -2683,10 +2720,12 @@ var webhook = {
 	// connect generates a secret rather than proving a credential.
 	hooks : {
 		auth : {
-			// Minting and clearing a secret needs no vendor call, so the api's own
-			// handler does both.
-			connect : {},
-			disconnect : {},
+			// FALSE, NOT {}. There is no vendor here at all — connecting mints a
+			// secret and disconnecting clears it, both done by the api's own
+			// handler. `{}` would promise a body implemented elsewhere, and none
+			// exists or could.
+			connect : false,
+			disconnect : false,
 			probe : false,
 			scopes : false,
 			// Nothing to mint. Connecting generates a secret; there is no vendor.

package/dist/connections/index.d.ts

@@ -603,7 +603,13 @@ var attentive = {
 	// connection DOCUMENT carries its own `errors` array and is spread OVER the
 	// resolved manifest downstream, so a top-level one would never render.
 	content : {
-		confirm : 'Disconnecting revokes Drawbridge\'s access to your Attentive account. Your subscribers stay in both Attentive and Drawbridge — neither list is deleted.',
+		// SAYS WHAT ACTUALLY HAPPENS. This used to promise that disconnecting
+		// revokes Drawbridge's access, and it cannot: Attentive documents no
+		// revocation endpoint, and their authentication page states an access
+		// token "does not expire". So the grant survives a disconnect forever
+		// unless the merchant removes the integration at Attentive, and the copy
+		// has to say so rather than let them believe otherwise.
+		confirm : 'Disconnecting removes Drawbridge\'s stored Attentive token. Attentive does not offer a way for us to revoke it, so remove the Drawbridge integration in Attentive as well if you want its access fully withdrawn. Your subscribers stay in both Attentive and Drawbridge — neither list is deleted.',
 		description : [
 			'Attentive is where your SMS marketing lives, and this connection is becoming the way your Drawbridge contacts sync into an Attentive segment.',
 			'You authorize Drawbridge from inside Attentive and can revoke that access there at any time. Drawbridge never sees or stores your Attentive password.',
@@ -645,8 +651,15 @@ var attentive = {
 			// account-identity endpoint to enrich them with — Klaviyo's connect
 			// reads the account name back; this has nothing cited to read. The
 			// callback stores the tokens and skips enrichment on `unimplemented`.
-			connect : {},
-			disconnect : {},
+			// FALSE, NOT {}. `{}` means "supported, implemented in the repo with the
+			// dependencies", and nothing anywhere implements either of these —
+			// there is nothing for them to do. The exchange already yields the
+			// tokens and Attentive documents no account-identity endpoint to
+			// enrich them with, so connect has nothing to add; and they document
+			// no revocation endpoint at all, so disconnect has nothing to call.
+			// Recorded as a decision rather than left as an unkept promise.
+			connect : false,
+			disconnect : false,
 			probe : false,
 			scopes : false,
 			// THE ONE THING WRAPPED, and it is about the response rather than the
@@ -2018,10 +2031,14 @@ var mailchimp = {
 	hooks : {
 
 		auth : {
-			// Implemented outside this package: storing a typed key needs no vendor
-			// call, so the api's own form handler does it.
-			connect : {},
-			disconnect : {},
+			// FALSE, NOT {}. `{}` promises an implementation living in the repo that
+			// holds the dependencies, and there is no implementation anywhere
+			// because there is nothing to implement: storing and clearing a typed
+			// key needs no vendor call, and the api's own form handler does it.
+			// Declaring `{}` made the coverage check chase a body that does not
+			// exist, and made a caller wait on an answer that never comes.
+			connect : false,
+			disconnect : false,
 			probe : false,
 			scopes : false,
 			// Keys today. When Mailchimp's OAuth lands this becomes a wrapper that
@@ -2322,10 +2339,30 @@ var shopify = {
 			// re-registers rather than answering "is this token still good", and
 			// scope drift is its own hook because a token can be perfectly valid
 			// while the grant is too narrow.
-			connect : {},
-			disconnect : {},
+			//
+			// connect and disconnect are FALSE rather than `{}`: there is nothing to
+			// call on either side. The install already hands the callback everything
+			// it stores, and a Shopify grant is withdrawn by UNINSTALLING the app in
+			// Shopify admin — which Drawbridge learns about from the app_uninstalled
+			// webhook rather than by asking. `{}` claimed a body implemented
+			// elsewhere; none exists, and none could.
+			connect : false,
+			disconnect : false,
 			probe : false,
-			scopes : {},
+
+			// WHETHER THE GRANT IS STILL WIDE ENOUGH. A token can be perfectly valid
+			// and still too narrow — a deploy that adds a scope leaves every existing
+			// install short of it, and no webhook fires to say so.
+			//
+			// The comparison is the vendor's, so it belongs here. Reading WHICH
+			// scopes a store granted is not: that lives in the `shop` collection and
+			// needs a controller, which is precisely what a hook in a published
+			// package must not be handed. The caller reads the grant and passes the
+			// string; this answers what is missing from it.
+			//
+			// `shopify` is injected for the same reason it is everywhere else — this
+			// package cannot import @drawbridge/shopify, which depends on it.
+			scopes : ({ scope, shopify }) => ( scope ? shopify.oauth.missingScopes( scope ) : null ),
 			// Shopify's install grant is exchanged inside its own app flow, not
 			// through the shared OAuth runner.
 			token : false
@@ -2683,10 +2720,12 @@ var webhook = {
 	// connect generates a secret rather than proving a credential.
 	hooks : {
 		auth : {
-			// Minting and clearing a secret needs no vendor call, so the api's own
-			// handler does both.
-			connect : {},
-			disconnect : {},
+			// FALSE, NOT {}. There is no vendor here at all — connecting mints a
+			// secret and disconnecting clears it, both done by the api's own
+			// handler. `{}` would promise a body implemented elsewhere, and none
+			// exists or could.
+			connect : false,
+			disconnect : false,
 			probe : false,
 			scopes : false,
 			// Nothing to mint. Connecting generates a secret; there is no vendor.

package/dist/connections/index.js

@@ -408,7 +408,13 @@ var attentive_default2 = {
   // connection DOCUMENT carries its own `errors` array and is spread OVER the
   // resolved manifest downstream, so a top-level one would never render.
   content: {
-    confirm: "Disconnecting revokes Drawbridge's access to your Attentive account. Your subscribers stay in both Attentive and Drawbridge \u2014 neither list is deleted.",
+    // SAYS WHAT ACTUALLY HAPPENS. This used to promise that disconnecting
+    // revokes Drawbridge's access, and it cannot: Attentive documents no
+    // revocation endpoint, and their authentication page states an access
+    // token "does not expire". So the grant survives a disconnect forever
+    // unless the merchant removes the integration at Attentive, and the copy
+    // has to say so rather than let them believe otherwise.
+    confirm: "Disconnecting removes Drawbridge's stored Attentive token. Attentive does not offer a way for us to revoke it, so remove the Drawbridge integration in Attentive as well if you want its access fully withdrawn. Your subscribers stay in both Attentive and Drawbridge \u2014 neither list is deleted.",
     description: [
       "Attentive is where your SMS marketing lives, and this connection is becoming the way your Drawbridge contacts sync into an Attentive segment.",
       "You authorize Drawbridge from inside Attentive and can revoke that access there at any time. Drawbridge never sees or stores your Attentive password.",
@@ -449,8 +455,15 @@ var attentive_default2 = {
       // account-identity endpoint to enrich them with — Klaviyo's connect
       // reads the account name back; this has nothing cited to read. The
       // callback stores the tokens and skips enrichment on `unimplemented`.
-      connect: {},
-      disconnect: {},
+      // FALSE, NOT {}. `{}` means "supported, implemented in the repo with the
+      // dependencies", and nothing anywhere implements either of these —
+      // there is nothing for them to do. The exchange already yields the
+      // tokens and Attentive documents no account-identity endpoint to
+      // enrich them with, so connect has nothing to add; and they document
+      // no revocation endpoint at all, so disconnect has nothing to call.
+      // Recorded as a decision rather than left as an unkept promise.
+      connect: false,
+      disconnect: false,
       probe: false,
       scopes: false,
       // THE ONE THING WRAPPED, and it is about the response rather than the
@@ -2120,10 +2133,14 @@ var mailchimp_default2 = {
   // contacts.sync are the first to flip.
   hooks: {
     auth: {
-      // Implemented outside this package: storing a typed key needs no vendor
-      // call, so the api's own form handler does it.
-      connect: {},
-      disconnect: {},
+      // FALSE, NOT {}. `{}` promises an implementation living in the repo that
+      // holds the dependencies, and there is no implementation anywhere
+      // because there is nothing to implement: storing and clearing a typed
+      // key needs no vendor call, and the api's own form handler does it.
+      // Declaring `{}` made the coverage check chase a body that does not
+      // exist, and made a caller wait on an answer that never comes.
+      connect: false,
+      disconnect: false,
       probe: false,
       scopes: false,
       // Keys today. When Mailchimp's OAuth lands this becomes a wrapper that
@@ -2344,10 +2361,29 @@ var shopify_default2 = {
       // re-registers rather than answering "is this token still good", and
       // scope drift is its own hook because a token can be perfectly valid
       // while the grant is too narrow.
-      connect: {},
-      disconnect: {},
+      //
+      // connect and disconnect are FALSE rather than `{}`: there is nothing to
+      // call on either side. The install already hands the callback everything
+      // it stores, and a Shopify grant is withdrawn by UNINSTALLING the app in
+      // Shopify admin — which Drawbridge learns about from the app_uninstalled
+      // webhook rather than by asking. `{}` claimed a body implemented
+      // elsewhere; none exists, and none could.
+      connect: false,
+      disconnect: false,
       probe: false,
-      scopes: {},
+      // WHETHER THE GRANT IS STILL WIDE ENOUGH. A token can be perfectly valid
+      // and still too narrow — a deploy that adds a scope leaves every existing
+      // install short of it, and no webhook fires to say so.
+      //
+      // The comparison is the vendor's, so it belongs here. Reading WHICH
+      // scopes a store granted is not: that lives in the `shop` collection and
+      // needs a controller, which is precisely what a hook in a published
+      // package must not be handed. The caller reads the grant and passes the
+      // string; this answers what is missing from it.
+      //
+      // `shopify` is injected for the same reason it is everywhere else — this
+      // package cannot import @drawbridge/shopify, which depends on it.
+      scopes: ({ scope, shopify }) => scope ? shopify.oauth.missingScopes(scope) : null,
       // Shopify's install grant is exchanged inside its own app flow, not
       // through the shared OAuth runner.
       token: false
@@ -2810,10 +2846,12 @@ var webhook_default = {
   // connect generates a secret rather than proving a credential.
   hooks: {
     auth: {
-      // Minting and clearing a secret needs no vendor call, so the api's own
-      // handler does both.
-      connect: {},
-      disconnect: {},
+      // FALSE, NOT {}. There is no vendor here at all — connecting mints a
+      // secret and disconnecting clears it, both done by the api's own
+      // handler. `{}` would promise a body implemented elsewhere, and none
+      // exists or could.
+      connect: false,
+      disconnect: false,
       probe: false,
       scopes: false,
       // Nothing to mint. Connecting generates a secret; there is no vendor.

package/package.json

@@ -210,5 +210,5 @@
     "test": ". \"$HOME/.nvm/nvm.sh\" && nvm use && node --test"
   },
   "types": "dist/index.d.ts",
-  "version": "0.0.115"
+  "version": "0.0.116"
 }