@drawbridge/drawbridge-utils 0.0.161 → 0.0.162

package/dist/notification.cjs

@@ -77,16 +77,12 @@ var messageWarnings = ({ message }) => {
 };
 var notificationWarnings = ({
   brand,
-  channel = "email",
   message,
   subject
-} = {}) => {
-  if (channel !== "email") return { message: [], subject: [] };
-  return {
-    message: messageWarnings({ message }),
-    subject: subjectWarnings({ brand, subject })
-  };
-};
+} = {}) => ({
+  message: messageWarnings({ message }),
+  subject: subjectWarnings({ brand, subject })
+});
 // Annotate the CommonJS export names for ESM import in node:
 0 && (module.exports = {
   notificationWarnings

package/dist/notification.d.cts

@@ -131,25 +131,32 @@ const messageWarnings = ({ message }) => {
 // ONE ENTRY POINT, answering per field so each warning renders against the
 // input it is about rather than as a pile at the bottom of the form.
 //
-// `channel` is accepted and only 'email' is implemented. SMS is a genuinely
-// different problem — carriers filter on SHAFT categories, link shorteners and
-// opt-out wording, none of which these rules look at — and returning email
-// advice for an SMS would be confidently wrong. It returns nothing instead,
-// until someone writes the carrier rules properly.
+// NO CHANNEL ARGUMENT, deliberately, and it is worth saying why since one was
+// tried twice.
+//
+// First it gated SMS to silence, on the grounds that carriers filter on things
+// these rules do not look at. That much is true, and it does not follow:
+// shouting, repeated punctuation, currency amounts and scam-shaped phrasing
+// matter at least as much on a phone, and an unbranded text is the exact shape
+// of a smishing attempt. Then a hedge value was added for copy that could go
+// either way, a caller passed it to a build that did not have it, and a whole
+// form went quiet with nothing to show for the caution.
+//
+// Every rule here is one a person would want to hear wherever the words end up.
+// Sorting them by channel bought accuracy on a single warning — the subject
+// display limit, which is really an email idea — and cost the other six.
+//
+// SMS still has no rules of its OWN: SHAFT categories, link shorteners, opt-out
+// wording, and the segment mechanics where one emoji drops the limit from 160
+// characters to 70. Those belong with the SMS connection work rather than here,
+// and their absence is a reason to write them, not to stay quiet meanwhile.
 const notificationWarnings = ({
 	brand,
-	channel = 'email',
 	message,
 	subject
-} = {}) => {
-
-	if( channel !== 'email' ) return { message : [], subject : [] };
-
-	return {
-		message : messageWarnings({ message }),
-		subject : subjectWarnings({ brand, subject })
-	};
-
-};
+} = {}) => ({
+	message : messageWarnings({ message }),
+	subject : subjectWarnings({ brand, subject })
+});
 
 export { notificationWarnings };

package/dist/notification.d.ts

@@ -131,25 +131,32 @@ const messageWarnings = ({ message }) => {
 // ONE ENTRY POINT, answering per field so each warning renders against the
 // input it is about rather than as a pile at the bottom of the form.
 //
-// `channel` is accepted and only 'email' is implemented. SMS is a genuinely
-// different problem — carriers filter on SHAFT categories, link shorteners and
-// opt-out wording, none of which these rules look at — and returning email
-// advice for an SMS would be confidently wrong. It returns nothing instead,
-// until someone writes the carrier rules properly.
+// NO CHANNEL ARGUMENT, deliberately, and it is worth saying why since one was
+// tried twice.
+//
+// First it gated SMS to silence, on the grounds that carriers filter on things
+// these rules do not look at. That much is true, and it does not follow:
+// shouting, repeated punctuation, currency amounts and scam-shaped phrasing
+// matter at least as much on a phone, and an unbranded text is the exact shape
+// of a smishing attempt. Then a hedge value was added for copy that could go
+// either way, a caller passed it to a build that did not have it, and a whole
+// form went quiet with nothing to show for the caution.
+//
+// Every rule here is one a person would want to hear wherever the words end up.
+// Sorting them by channel bought accuracy on a single warning — the subject
+// display limit, which is really an email idea — and cost the other six.
+//
+// SMS still has no rules of its OWN: SHAFT categories, link shorteners, opt-out
+// wording, and the segment mechanics where one emoji drops the limit from 160
+// characters to 70. Those belong with the SMS connection work rather than here,
+// and their absence is a reason to write them, not to stay quiet meanwhile.
 const notificationWarnings = ({
 	brand,
-	channel = 'email',
 	message,
 	subject
-} = {}) => {
-
-	if( channel !== 'email' ) return { message : [], subject : [] };
-
-	return {
-		message : messageWarnings({ message }),
-		subject : subjectWarnings({ brand, subject })
-	};
-
-};
+} = {}) => ({
+	message : messageWarnings({ message }),
+	subject : subjectWarnings({ brand, subject })
+});
 
 export { notificationWarnings };

package/dist/notification.js

@@ -54,16 +54,12 @@ var messageWarnings = ({ message }) => {
 };
 var notificationWarnings = ({
   brand,
-  channel = "email",
   message,
   subject
-} = {}) => {
-  if (channel !== "email") return { message: [], subject: [] };
-  return {
-    message: messageWarnings({ message }),
-    subject: subjectWarnings({ brand, subject })
-  };
-};
+} = {}) => ({
+  message: messageWarnings({ message }),
+  subject: subjectWarnings({ brand, subject })
+});
 export {
   notificationWarnings
 };

package/package.json

@@ -226,5 +226,5 @@
     "prepublishOnly": ". \"$HOME/.nvm/nvm.sh\" && nvm use && tsup && node --test"
   },
   "types": "dist/index.d.ts",
-  "version": "0.0.161"
+  "version": "0.0.162"
 }