@pushwoosh/smart-components-kit 1.3.6 → 1.3.7

package/mmsAttachments/index.d.ts

@@ -1 +1 @@
-export { MMS_ALLOWED_EXTENSIONS, MMS_MAX_ATTACHMENTS, MMS_SAFE_FILE_SIZE_BYTES, MMS_SUBJECT_MAX_ASCII_LENGTH, MMS_SUBJECT_MAX_UNICODE_LENGTH, getMmsSubjectLength, getMmsSubjectMaxLength, isMmsAttachmentOversized, isMmsAttachmentUrl, isMmsMessageAtValid, isMmsSubjectTooLong, } from './rules';
+export { MMS_ALLOWED_EXTENSIONS, MMS_MAX_ATTACHMENTS, MMS_MAX_FILE_SIZE_BYTES, MMS_SUBJECT_MAX_ASCII_LENGTH, MMS_SUBJECT_MAX_UNICODE_LENGTH, getMmsSubjectLength, getMmsSubjectMaxLength, isMmsAttachmentOversized, isMmsAttachmentUrl, isMmsMessageAtValid, isMmsSubjectTooLong, } from './rules';

package/mmsAttachments/index.js

@@ -1 +1 @@
-export { MMS_ALLOWED_EXTENSIONS, MMS_MAX_ATTACHMENTS, MMS_SAFE_FILE_SIZE_BYTES, MMS_SUBJECT_MAX_ASCII_LENGTH, MMS_SUBJECT_MAX_UNICODE_LENGTH, getMmsSubjectLength, getMmsSubjectMaxLength, isMmsAttachmentOversized, isMmsAttachmentUrl, isMmsMessageAtValid, isMmsSubjectTooLong } from './rules';
+export { MMS_ALLOWED_EXTENSIONS, MMS_MAX_ATTACHMENTS, MMS_MAX_FILE_SIZE_BYTES, MMS_SUBJECT_MAX_ASCII_LENGTH, MMS_SUBJECT_MAX_UNICODE_LENGTH, getMmsSubjectLength, getMmsSubjectMaxLength, isMmsAttachmentOversized, isMmsAttachmentUrl, isMmsMessageAtValid, isMmsSubjectTooLong } from './rules';

package/mmsAttachments/rules.d.ts

@@ -8,20 +8,20 @@ export declare const MMS_SUBJECT_MAX_ASCII_LENGTH = 40;
 export declare const MMS_SUBJECT_MAX_UNICODE_LENGTH = 13;
 export declare const MMS_ALLOWED_EXTENSIONS: string[];
 /**
- * Attachments above this stay compatible with older networks and handsets. It is a
- * recommendation, not a provider limit — warn, never block.
+ * The provider rejects anything heavier, so an oversized attachment fails the whole send.
+ * Media-library sizes are not always known, so the forms warn on it instead of blocking.
  */
-export declare const MMS_SAFE_FILE_SIZE_BYTES: number;
+export declare const MMS_MAX_FILE_SIZE_BYTES: number;
 /**
  * The provider downloads the attachment itself, so it has to be a public https url whose
  * *path* ends with a supported image extension. Checking the path (not the whole url) matches
  * the backend and keeps query strings — signatures, cache busters — from passing as extensions.
  *
- * The same rule also hides WebP and the legacy media-library files stored without an extension:
- * both are fetchable, neither is accepted downstream.
+ * PNG, JPEG, WebP and the legacy media-library files stored without an extension drop out
+ * here: all of them are fetchable, none is decoded by the provider.
  */
 export declare const isMmsAttachmentUrl: (url: string) => boolean;
-/** Whether the file is large enough to warrant the "may not arrive" warning. */
+/** Whether the file is over the provider's size limit and will be rejected on send. */
 export declare const isMmsAttachmentOversized: (file: MediaFile) => boolean;
 /**
  * Subject length budget: the provider counts non-ASCII subjects against a much shorter

package/mmsAttachments/rules.js

@@ -5,19 +5,19 @@
 export const MMS_MAX_ATTACHMENTS = 3;
 export const MMS_SUBJECT_MAX_ASCII_LENGTH = 40;
 export const MMS_SUBJECT_MAX_UNICODE_LENGTH = 13;
-export const MMS_ALLOWED_EXTENSIONS = ['.jpg', '.jpeg', '.png', '.gif'];
+export const MMS_ALLOWED_EXTENSIONS = ['.jpg', '.gif'];
 /**
- * Attachments above this stay compatible with older networks and handsets. It is a
- * recommendation, not a provider limit — warn, never block.
+ * The provider rejects anything heavier, so an oversized attachment fails the whole send.
+ * Media-library sizes are not always known, so the forms warn on it instead of blocking.
  */
-export const MMS_SAFE_FILE_SIZE_BYTES = 300 * 1024;
+export const MMS_MAX_FILE_SIZE_BYTES = 200 * 1024;
 /**
  * The provider downloads the attachment itself, so it has to be a public https url whose
  * *path* ends with a supported image extension. Checking the path (not the whole url) matches
  * the backend and keeps query strings — signatures, cache busters — from passing as extensions.
  *
- * The same rule also hides WebP and the legacy media-library files stored without an extension:
- * both are fetchable, neither is accepted downstream.
+ * PNG, JPEG, WebP and the legacy media-library files stored without an extension drop out
+ * here: all of them are fetchable, none is decoded by the provider.
  */
 export const isMmsAttachmentUrl = url => {
   let parsed;
@@ -30,8 +30,8 @@ export const isMmsAttachmentUrl = url => {
   const path = parsed.pathname.toLowerCase();
   return MMS_ALLOWED_EXTENSIONS.some(extension => path.endsWith(extension));
 };
-/** Whether the file is large enough to warrant the "may not arrive" warning. */
-export const isMmsAttachmentOversized = file => file.fileSize > MMS_SAFE_FILE_SIZE_BYTES;
+/** Whether the file is over the provider's size limit and will be rejected on send. */
+export const isMmsAttachmentOversized = file => file.fileSize > MMS_MAX_FILE_SIZE_BYTES;
 /**
  * Subject length budget: the provider counts non-ASCII subjects against a much shorter
  * limit, so a single non-ASCII character drops the whole subject to 13.

package/package.json

@@ -52,5 +52,5 @@
     "react": "^16.14.0 || ^18.0.0",
     "react-dom": "^16.14.0 || ^18.0.0"
   },
-  "version": "1.3.6"
+  "version": "1.3.7"
 }