@5minds/node-red-contrib-processcube-tools 1.0.2-feature-8805f0-mfnm2ko3 → 1.0.2-feature-6cf243-mfp26zop

package/email-sender/email-sender.html

@@ -222,24 +222,24 @@
 </script>
 
 <script type="text/html" data-help-name="email-sender">
-    <p>
-        A custom Node-RED node that simplifies sending emails using an SMTP server.
-    </p>
+    <p>A custom Node-RED node that simplifies sending emails using an SMTP server.</p>
 
     <h3>Description</h3>
     <p>
-        The <b>email-sender</b> node is designed to send emails from your Node-RED flows. It supports a wide range of features, including sending HTML content, adding attachments, and using flexible configurations for all email and SMTP settings. All fields are <b>typed inputs</b>, meaning you can pull values from different sources like <code>msg</code> properties, <code>flow</code>/<code>global</code> context, or environment variables.
+        The <b>email-sender</b> node is designed to send emails from your Node-RED flows. It supports a wide range of
+        features, including sending HTML content, adding attachments, and using flexible configurations for all email
+        and SMTP settings. All fields are <b>typed inputs</b>, meaning you can pull values from different sources like
+        <code>msg</code> properties, <code>flow</code>/<code>global</code> context, or environment variables.
     </p>
 
     <h3>Inputs</h3>
     <p>
-        This node accepts a message (<code>msg</code>) as input. The node is triggered when it receives a message. The properties of the incoming message can be used to set the email's configuration fields.
+        This node accepts a message (<code>msg</code>) as input. The node is triggered when it receives a message. The
+        properties of the incoming message can be used to set the email's configuration fields.
     </p>
 
     <h3>Outputs</h3>
-    <p>
-        This node sends one message upon successful execution.
-    </p>
+    <p>This node sends one message upon successful execution.</p>
     <dl class="message-properties">
         <dt>payload <span class="property-type">any</span></dt>
         <dd>The <code>payload</code> of the original message is passed through to the next node.</dd>
@@ -250,7 +250,8 @@
 
     <h3>Configuration</h3>
     <p>
-        All configuration fields are <b>typed inputs</b>, allowing you to set a <b>static value</b> or pull data dynamically from a <b>message</b>, <b>flow</b>, <b>global</b> context, or <b>environment variable</b>.
+        All configuration fields are <b>typed inputs</b>, allowing you to set a <b>static value</b> or pull data
+        dynamically from a <b>message</b>, <b>flow</b>, <b>global</b> context, or <b>environment variable</b>.
     </p>
 
     <h4>Mail Configuration</h4>
@@ -274,7 +275,10 @@
         <dt>HTML Content <span class="property-type">string | variable</span></dt>
         <dd>The full HTML body of the email.</dd>
         <dt>Attachments <i>(Optional)</i> <span class="property-type">array | variable</span></dt>
-        <dd>A list of file attachments. This field should be an array of attachment objects. Each object must contain <code>filename</code>, <code>content</code> (the file's data), and optionally <code>contentType</code>.</dd>
+        <dd>
+            A list of file attachments. This field should be an array of attachment objects. Each object must contain
+            <code>filename</code>, <code>content</code> (the file's data), and optionally <code>contentType</code>.
+        </dd>
     </dl>
 
     <h4>SMTP Configuration</h4>
@@ -286,22 +290,43 @@
         <dt>User <span class="property-type">string | variable</span></dt>
         <dd>The username for SMTP authentication.</dd>
         <dt>Password <span class="property-type">password | variable</span></dt>
-        <dd>The password for SMTP authentication. This is a secure field and its value will not be shown after deployment.</dd>
+        <dd>
+            The password for SMTP authentication. This is a secure field and its value will not be shown after
+            deployment.
+        </dd>
         <dt>SSL/TLS (Secure) <span class="property-type">boolean | variable</span></dt>
         <dd>Enables a secure connection. Set this to <code>true</code> to use SSL/TLS encryption.</dd>
         <dt>Reject Unauthorized <span class="property-type">boolean | variable</span></dt>
-        <dd>If <code>true</code>, the server's certificate is rejected if it isn't authorized by a trusted Certificate Authority (CA). Set this to <code>false</code> only if you know the server's certificate is self-signed or not from a trusted CA.</dd>
+        <dd>
+            If <code>true</code>, the server's certificate is rejected if it isn't authorized by a trusted Certificate
+            Authority (CA). Set this to <code>false</code> only if you know the server's certificate is self-signed or
+            not from a trusted CA.
+        </dd>
     </dl>
 
     <h3>Usage Notes</h3>
     <ul>
-        <li><b>Dynamic Content</b>: You can use a <b>Template node</b> before the <b>email-sender</b> node to generate dynamic HTML content for your emails, using <code>msg</code> properties to fill in placeholders.</li>
-        <li><b>Testing</b>: When testing, use a free service like <a href="https://mailtrap.io" target="_blank">Mailtrap</a> to avoid sending real emails. This allows you to inspect the email and its content without cluttering your inbox.</li>
-        <li><b>Troubleshooting</b>: If you encounter a <code>Missing required IMAP config</code> error, double-check that all required fields are correctly configured and have values.</li>
+        <li>
+            <b>Dynamic Content</b>: You can use a <b>Template node</b> before the <b>email-sender</b> node to generate
+            dynamic HTML content for your emails, using <code>msg</code> properties to fill in placeholders.
+        </li>
+        <li>
+            <b>Testing</b>: When testing, use a free service like
+            <a href="https://mailtrap.io" target="_blank">Mailtrap</a> to avoid sending real emails. This allows you to
+            inspect the email and its content without cluttering your inbox.
+        </li>
+        <li>
+            <b>Troubleshooting</b>: If you encounter a <code>Missing required IMAP config</code> error, double-check
+            that all required fields are correctly configured and have values.
+        </li>
     </ul>
 
     <h3>Example</h3>
     <p>A basic flow could look like this:</p>
     <code>Inject Node</code> ➡️ <code>Change Node</code> ➡️ <code>email-sender Node</code>
-    <p>In the <b>Change Node</b>, you can set <code>msg.payload</code> to your email's content and <code>msg.topic</code> to the subject. The <b>email-sender</b> node can then be configured to use these message properties as its input.</p>
+    <p>
+        In the <b>Change Node</b>, you can set <code>msg.payload</code> to your email's content and
+        <code>msg.topic</code> to the subject. The <b>email-sender</b> node can then be configured to use these message
+        properties as its input.
+    </p>
 </script>

package/email-sender/email-sender.js

@@ -48,7 +48,7 @@ module.exports = function (RED) {
             // Handle attachments and format them for Nodemailer
             let processedAttachments = [];
 
-            let parsedAttachments = config.attachments;
+            let parsedAttachments = attachments;
 
             if (config.attachmentsType === 'json' && typeof parsedAttachments === 'string') {
                 try {

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@5minds/node-red-contrib-processcube-tools",
-    "version": "1.0.2-feature-8805f0-mfnm2ko3",
+    "version": "1.0.2-feature-6cf243-mfp26zop",
     "license": "MIT",
     "description": "Node-RED tools nodes for ProcessCube",
     "scripts": {