<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dohrnyx on Medium]]></title>
        <description><![CDATA[Stories by Dohrnyx on Medium]]></description>
        <link>https://medium.com/@dohrnyx.social?source=rss-87f8eed106f5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RCMET7dBSWhw5IUpW6rwVg.jpeg</url>
            <title>Stories by Dohrnyx on Medium</title>
            <link>https://medium.com/@dohrnyx.social?source=rss-87f8eed106f5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:08:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dohrnyx.social/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Migration, Seeder and Factory Creator In Nodejs]]></title>
            <link>https://medium.com/@dohrnyx.social/migration-seeder-and-factory-creator-in-nodejs-07669929023a?source=rss-87f8eed106f5------2</link>
            <guid isPermaLink="false">https://medium.com/p/07669929023a</guid>
            <category><![CDATA[npm-package]]></category>
            <category><![CDATA[migration-and-seeder]]></category>
            <category><![CDATA[nodejs-packages]]></category>
            <category><![CDATA[dohrnyx]]></category>
            <dc:creator><![CDATA[Dohrnyx]]></dc:creator>
            <pubDate>Tue, 13 Oct 2026 10:29:23 GMT</pubDate>
            <atom:updated>2026-10-13T10:29:23.853Z</atom:updated>
            <content:encoded><![CDATA[<h4>Dohrnyx | NPM Package (<a href="https://www.npmjs.com/package/migration-seeder-factory">migration-seeder-factory</a>):</h4><p>You can use the “migration-seeder-factory” package for Node.js, which helps you create migrations and seed data without needing in-depth knowledge of all db query and datatype syntaxes. Simply follow the provided syntax, and you’re good to go.</p><h3># Migration, Seeder, and Factory Creator</h3><p>This package provides an easy way to generate migrations, seeders, and factories using built-in commands in Node.js . Developed by <a href="https://dohrnyx.com/"><strong>Dohrnyx</strong></a>, this tool streamlines database management for your applications.</p><h3>Note: MongoDB functionality will be available soon. Meanwhile, all features for MySQL and PostgreSQL are fully functional and ready to use.</h3><h3>Features</h3><ul><li>Generate migrations, seeders, and factories effortlessly</li><li>Simple CLI commands for quick setup</li><li>Compatible with Node.js version v18.20.7 and later.</li><li>Supports PostgreSQL, MySQL</li></ul><h3>Installation</h3><pre>npm install migration-seeder-factory</pre><h3>How to Use After Installation</h3><h3>Usage</h3><p>Run the following commands to create respective database assets:</p><p>Environment variables required for database connection that must be set in your `.env` file.</p><pre># Currently This Variable For MongoDB Not in Use, But Will Be Available Soon<br>MONGO_CONNECTION_URL=</pre><pre>MYSQL_HOST=<br>MYSQL_PORT=<br>MYSQL_USER=<br>MYSQL_PASSWORD=<br>MYSQL_DATABASE=</pre><pre>PG_HOST=<br>PG_PORT=<br>PG_USER=<br>PG_PASSWORD=<br>PG_DATABASE=</pre><pre>#postgres or mysql<br>DEFAULT_DB_TYPE=</pre><h3>Note</h3><p>--db= - Not required. If you want, you can set the default database via your .env variable: <strong>DEFAULT_DB_TYPE</strong>.</p><h3>Commands</h3><h4>Create a Migration:</h4><p>For MySQL:</p><pre>npx nexxt make:migration create_sites_table --db=mysql</pre><p>For PostgreSQL:</p><pre>npx nexxt make:migration create_sites_table --db=postgres</pre><h4>Run Migrations:</h4><p>For MySQL:</p><p>This will execute all files from the migration folder based on the database type.</p><pre>npx nexxt migrate --db=mysql</pre><p>This will execute a specific migration file.</p><pre>npx nexxt migrate 20250223154656_create_site_table --db=mysql</pre><p>For PostgreSQL:</p><p>This will execute all files from the migration folder based on the database type.</p><pre>npx nexxt migrate --db=postgres</pre><p>This will execute a specific migration file.</p><pre>npx nexxt migrate 20250223154656_create_site_table --db=postgres</pre><h4>Rollback Migrations:</h4><p>After “migrate:rollback” — you can specify a filename to roll back a particular migration; otherwise, it will roll back all migrations.</p><p>For MySQL:</p><pre>npx nexxt migrate:rollback --db=mysql</pre><p>This will execute a specific file.</p><pre>npx nexxt migrate:rollback create_sites_table --db=mysql</pre><p>For PostgreSQL:</p><pre>npx nexxt migrate:rollback --db=postgres</pre><p>This will execute a specific file.</p><pre>npx nexxt migrate:rollback create_sites_table --db=postgres</pre><h4>Create a Seeder:</h4><p>For MySQL:</p><pre>npx nexxt make:seeder sites_seeder --db=mysql</pre><p>For PostgreSQL:</p><pre>npx nexxt make:seeder sites_seeder --db=postgres</pre><h4>Create Factory:</h4><p>For MySQL:</p><pre>npx nexxt make:factory sites_factory</pre><h4>Run Seeders:</h4><p>For MySQL:</p><pre>npx nexxt seed --db=mysql</pre><p>This will execute a specific file.</p><pre>npx nexxt seed sites_seeder --db=mysql</pre><p>For PostgreSQL:</p><pre>npx nexxt seed --db=postgres</pre><p>This will execute a specific file.</p><pre>npx nexxt seed sites_seeder --db=postgres</pre><h3>Object that help for migrate</h3><p>You can use it as needed, as some keys may not be required for PostgreSQL or MySQL. However, all keys are defined for completeness.</p><pre>{<br>  &quot;migrations&quot;: [<br>    {<br>      &quot;action&quot;: &quot;create&quot;,<br>      &quot;table&quot;: &quot;sites&quot;,<br>      &quot;columns&quot;: [<br>        {<br>          &quot;name&quot;: &quot;id&quot;,<br>          &quot;type&quot;: &quot;int&quot;,<br>          &quot;primaryKey&quot;: true,<br>          &quot;autoIncrement&quot;: true<br>        },<br>        {<br>          &quot;name&quot;: &quot;name&quot;,<br>          &quot;type&quot;: &quot;varchar(255)&quot;,<br>          &quot;unique&quot;: true,<br>          &quot;nullable&quot;: false<br>        },<br>        {<br>          &quot;name&quot;: &quot;user_id&quot;,<br>          &quot;type&quot;: &quot;int&quot;,<br>          &quot;unsigned&quot;: true //this should be false when you use mysql<br>        },<br>        {<br>          &quot;name&quot;: &quot;age&quot;,<br>          &quot;type&quot;: &quot;varchar(100)&quot;,<br>          &quot;nullable&quot;: false,<br>          &quot;default&quot;: 0<br>        },<br>        {<br>          &quot;name&quot;: &quot;dob&quot;,<br>          &quot;type&quot;: &quot;date&quot;,<br>          &quot;nullable&quot;: true<br>        },<br>        {<br>          &quot;name&quot;: &quot;createdAt&quot;,<br>          &quot;type&quot;: &quot;timestamp&quot;,<br>          &quot;default&quot;: {<br>            &quot;value&quot;: &quot;CURRENT_TIMESTAMP&quot;<br>          }<br>        },<br>        {<br>          &quot;name&quot;: &quot;updatedAt&quot;,<br>          &quot;type&quot;: &quot;timestamp&quot;,<br>          &quot;default&quot;: {<br>            &quot;function&quot;: &quot;ON_UPDATE_TIMESTAMP&quot;<br>          }<br>        },<br>        {<br>          &quot;name&quot;: &quot;deletedAt&quot;,<br>          &quot;type&quot;: &quot;timestamp&quot;,<br>          &quot;nullable&quot;: true<br>        }<br>      ],<br>      &quot;indexes&quot;: [<br>        {<br>          &quot;name&quot;: &quot;idx_sites_name&quot;,<br>          &quot;columns&quot;: [<br>            &quot;name&quot;<br>          ],<br>          &quot;unique&quot;: true<br>        }<br>      ],<br>      &quot;foreignKeys&quot;: [<br>        {<br>          &quot;name&quot;: &quot;fk_sites_user&quot;,<br>          &quot;column&quot;: &quot;user_id&quot;,<br>          &quot;referenceTable&quot;: &quot;users&quot;,<br>          &quot;referenceColumn&quot;: &quot;id&quot;<br>        }<br>      ],<br>      &quot;engine&quot;: &quot;InnoDB&quot;,<br>      &quot;charset&quot;: &quot;utf8mb4&quot;<br>    },<br>    {<br>      &quot;action&quot;: &quot;alter&quot;,<br>      &quot;table&quot;: &quot;sites&quot;,<br>      &quot;changes&quot;: {<br>        &quot;add&quot;: [<br>          {<br>            &quot;name&quot;: &quot;email&quot;,<br>            &quot;type&quot;: &quot;varchar(100)&quot;,<br>            &quot;nullable&quot;: true,<br>            &quot;after&quot;: &quot;name&quot;<br>          },<br>          {<br>            &quot;name&quot;: &quot;owner_id&quot;,<br>            &quot;type&quot;: &quot;int&quot;,<br>            &quot;nullable&quot;: true,<br>            &quot;unsigned&quot;: true<br>          }<br>        ],<br>        &quot;modify&quot;: [<br>          {<br>            &quot;name&quot;: &quot;age&quot;,<br>            &quot;type&quot;: &quot;int&quot;,<br>            &quot;nullable&quot;: false,<br>            &quot;after&quot;: &quot;id&quot;<br>          }<br>        ],<br>        &quot;drop&quot;: [<br>          &quot;dob&quot;<br>        ],<br>        &quot;addForeignKeys&quot;: [<br>          {<br>            &quot;name&quot;: &quot;fk_sites_owner&quot;,<br>            &quot;column&quot;: &quot;owner_id&quot;,<br>            &quot;referenceTable&quot;: &quot;users&quot;,<br>            &quot;referenceColumn&quot;: &quot;id&quot;<br>          }<br>        ],<br>        &quot;dropForeignKeys&quot;: [<br>          &quot;fk_sites_user&quot;<br>        ],<br>        &quot;dropIndex&quot;: [<br>          &quot;idx_sites_name&quot;<br>        ]<br>      }<br>    }<br>  ],<br>  &quot;rollback&quot;: [<br>    {<br>      &quot;action&quot;: &quot;drop&quot;,<br>      &quot;table&quot;: &quot;sites&quot;,<br>      &quot;dropIfExists&quot;: true,<br>      &quot;ignoreForeignAndCascade&quot;: true<br>    }<br>  ]<br>}</pre><p>This JSON object represents a structured way to define database migrations, compatible with both MySQL and PostgreSQL. Below is a breakdown of each key and its purpose in generating database queries:</p><h3>Migrations</h3><p>The migrations array contains objects that define database schema changes.</p><h4>1. Create Table (action: &quot;create&quot;)</h4><p>Defines a new table (sites or whatever table name) with the following properties:</p><ul><li><strong>columns</strong>: Specifies the columns in the table.</li><li><strong>name</strong>: Column name.</li><li><strong>type</strong>: Data type (e.g., int, varchar(255), timestamp).</li><li><strong>primaryKey</strong>: Marks the column as a primary key.</li><li><strong>autoIncrement</strong>: Enables auto-incrementing for primary keys.</li><li><strong>unique</strong>: Enforces unique constraint.</li><li><strong>nullable</strong>: Determines if the column can store NULL values.</li><li><strong>default</strong>: Assigns a default value to the column.</li><li><strong>unsigned</strong>: Ensures only positive values (MySQL-specific).</li><li><strong>indexes</strong>: Defines indexes for faster queries.</li><li><strong>name</strong>: Index name.</li><li><strong>foreignKeys</strong>: Defines relationships between tables.</li><li><strong>name</strong>: Foreign key constraint name.</li><li><strong>column</strong>: Column in the sites table that references another table.</li><li><strong>referenceTable</strong>: Table being referenced.</li><li><strong>referenceColumn</strong>: Column in the referenced table.</li><li><strong>engine</strong>: Specifies the storage engine (MySQL-specific, e.g., InnoDB).</li><li><strong>charset</strong>: Defines the character encoding (e.g., utf8mb4).</li><li><strong>after</strong>: Specifies whether a column is being modified or added during an <strong>ALTER operation Only</strong>. You can define its position by placing it after a specific existing column. — (<strong>This works exclusively with the MySQL database type.)</strong></li></ul><h4>2. Alter Table (action: &quot;alter&quot;)</h4><p>Modifies the existing <em>sites or whatever table name</em> table:</p><ul><li><strong>add</strong>: Adds new columns (email, owner_id).</li><li><strong>modify</strong>: Changes column properties (age changed to int).</li><li><strong>drop</strong>: Removes columns (dob).</li><li><strong>addForeignKeys</strong>: Adds new foreign keys.</li><li><strong>dropForeignKeys</strong>: Removes existing foreign keys.</li><li><strong>dropIndex</strong>: Drops existing indexes.</li></ul><h3>Rollback</h3><p>Defines how to revert changes if needed:</p><ul><li><strong>action: &quot;drop&quot;</strong>: Drops the sites or whatever table name table.</li><li><strong>dropIfExists</strong>: Ensures the table is only dropped if it exists.</li><li><strong>ignoreForeignAndCascade</strong>: Ensures dependent records are removed properly.</li></ul><h3>Compatibility with MySQL &amp; PostgreSQL</h3><ul><li><strong>Compatible with Both:</strong></li><li>Table creation, column definitions, and modifications.</li><li>Indexing and foreign key constraints.</li></ul><p>This structure allows for seamless database migrations across MySQL and PostgreSQL. 🚀</p><h3>This Is for seeder and factory</h3><p>In this context, “factory” refers to the factory name that you need to create. You must specify the file name you want to execute.</p><h4>Seeder Object</h4><pre>{<br>  &quot;seed&quot;: [<br>    {<br>      &quot;table&quot;: &quot;sites&quot;,<br>      &quot;factory&quot;: &quot;users_factory&quot;,<br>      &quot;execution_count&quot;: 2,<br>      &quot;createOrUpdate&quot;: {<br>        &quot;matchColumns&quot;: [<br>          &quot;name&quot;<br>        ],<br>        &quot;operator&quot;: &quot;or&quot;<br>      },<br>      &quot;custom&quot;: {<br>        &quot;query&quot;: &quot;&quot;,<br>        &quot;execution_count&quot;: 0<br>      }<br>    },<br>    {<br>      &quot;table&quot;: &quot;sites&quot;,<br>      &quot;factory&quot;: &quot;users_factory&quot;,<br>      &quot;execution_count&quot;: 0,<br>      &quot;createOrUpdate&quot;: {<br>        &quot;matchColumns&quot;: [<br>          &quot;name&quot;,<br>          &quot;status&quot;<br>        ],<br>        &quot;operator&quot;: &quot;and&quot;<br>      },<br>      &quot;custom&quot;: {<br>        &quot;query&quot;: &quot;INSERT INTO space_types (name, status) VALUES (&#39;Test Name&#39;, 1)&quot;,<br>        &quot;execution_count&quot;: 1<br>      },<br>      &quot;referenceQuery&quot;: {<br>        &quot;query&quot;: &quot;INSERT INTO log (name, context) VALUES (&#39;{forRefName}&#39;, &#39;{context}_alias&#39;)&quot;,<br>        &quot;columns&quot; : {<br>          &quot;forRefName&quot; : &quot;name&quot;,<br>          &quot;context&quot;: &quot;context_id&quot;<br>        }<br>      }<br>    }<br>  ]<br>}</pre><h3>Keys and Their Uses</h3><h4>seed (Array)</h4><p>The seed array contains multiple objects, each specifying how data should be inserted into a particular table.</p><h4>Each Seed Object Contains:</h4><ul><li><strong>table (String)</strong><br>The name of the table where data will be inserted.<br><strong>Example:</strong> &quot;table&quot;: &quot;sites&quot; (Data will be inserted into the sites table).</li><li><strong>factory (String)</strong><br>Specifies the factory name used to generate data automatically. The factory must be predefined.<br><strong>Example:</strong> &quot;factory&quot;: &quot;users_factory&quot; (Uses the users_factory to generate data).</li><li><strong>execution_count (Integer)</strong><br>Determines how many times the factory should generate and insert data into the table.</li><li>&quot;execution_count&quot;: 2 → Runs the factory twice, inserting two records.</li><li>&quot;execution_count&quot;: 0 → Factory-based seeding is disabled for this entry (this will run 0 times, means this is in disable state).</li><li><strong>createOrUpdate (Object)</strong></li><li>the logic for checking whether a record already exists in the table before inserting or updating for that matched columns which is define in <em>factory file</em>.</li><li><strong>matchColumns</strong>: [&quot;name&quot;,&quot;status&quot;]</li><li>Specifies the columns used for matching existing records.</li><li><strong>operator</strong>: &quot;or&quot; / &quot;and&quot;</li><li>Determines how the match condition is applied (OR between conditions, meaning either status or name should match).</li><li>Determines how the match condition is applied (AND conditions, meaning status and name both should match).</li><li><strong>Custom:</strong></li><li><strong>query (String)</strong><br>A raw SQL query that will be executed directly instead of using a factory. This allows precise control over inserted data.</li></ul><pre>Example: &quot;custom&quot;: {<br>            &quot;query&quot;: &quot;INSERT INTO space_types (name, status) VALUES (&#39;Test Name&#39;, 1)&quot;,<br>          }</pre><ul><li><strong>execution_count (number)</strong><br>Determines how many times the factory should generate and insert data into the table.</li><li><strong>referenceQuery</strong><br>Use this option when you need to insert data into another table and want to reference values from the current table’s columns.</li></ul><pre>&quot;referenceQuery&quot;: {<br>  &quot;query&quot;: &quot;INSERT INTO log (name, context) VALUES (&#39;{forRefName}&#39;, &#39;{context}_alias&#39;)&quot;,<br>  &quot;columns&quot;: {<br>    &quot;forRefName&quot;: &quot;name&quot;,<br>    &quot;context&quot;: &quot;context_id&quot;<br>  }<br>}</pre><p>In this example:</p><ul><li>The query defines an SQL statement with placeholders wrapped in {}.</li><li>The columns object maps each placeholder (forRefName, context) to a column in the current table (name, context_id respectively).</li><li>When executed, the placeholders will be replaced with the values from the corresponding columns in the current table row.</li></ul><h4>Factory Object</h4><p>This defines the column information that you want to modify or affect.</p><pre>{<br>  &quot;columns&quot;: [<br>    {<br>      &quot;context_id&quot;: {<br>        &quot;fake&quot;: false,<br>        &quot;type&quot;: &quot;number&quot;,<br>        &quot;custom&quot;: {<br>          &quot;reference_table&quot;: {<br>            &quot;table&quot;: &quot;sites&quot;,<br>            &quot;column&quot;: &quot;id&quot;<br>          }<br>        }<br>      },<br>      &quot;first_name&quot;: {<br>        &quot;fake&quot;: false,<br>        &quot;type&quot;: &quot;&quot;,<br>        &quot;custom&quot;: &quot;{name}&quot;,<br>        &quot;convert_case&quot; : &quot;lower&quot;<br>      },<br>      &quot;name&quot;: {<br>        &quot;fake&quot;: true,<br>        &quot;type&quot;: &quot;string&quot;,<br>        &quot;custom&quot;: &quot;&quot;,<br>        &quot;manipulation&quot;: {<br>          &quot;regex&quot; : &quot;\\s&quot;,<br>          &quot;replace_with&quot; : &quot;-&quot;<br>        }<br>      },<br>      &quot;father_name&quot;: {<br>        &quot;fake&quot;: true,<br>        &quot;type&quot;: &quot;string&quot;,<br>        &quot;custom&quot;: &quot;&quot;,<br>        &quot;convert_case&quot; : &quot;lower&quot;<br>      },<br>      &quot;status&quot;: {<br>        &quot;fake&quot;: false,<br>        &quot;type&quot;: &quot;&quot;,<br>        &quot;custom&quot;: 1<br>      }<br>    }<br>  ]<br>}</pre><h3>Object Description for Column Data Generation</h3><p>This JSON object defines how column data should be generated for seeding purposes. It supports both fake (randomly generated) values and custom static values.</p><h3>Keys and Their Uses</h3><h4>columns (Array)</h4><p>The columns array contains objects that define <strong>how each column&#39;s data should be populated</strong>.</p><h4>Each Column Object Contains:</h4><ul><li><strong>column_name (Object)</strong><br>The key (e.g., &quot;name&quot; or &quot;age&quot;) represents the <strong>column name</strong> in the database.<br>Each column contains the following properties:</li><li><strong>fake (Boolean)</strong></li><li>true: The value will be randomly generated using a faker library.</li><li>false: The value is manually specified.</li><li><strong>type (String)</strong><br>Defines the type of data for this column.<br><strong>Example Types:</strong> &quot;string&quot;, &quot;number&quot;, &quot;boolean&quot;, &quot;date&quot; etc.</li></ul><pre>Here are all the supported types:</pre><pre>number<br>smallint<br>mediumint<br>bigint<br>tinyint<br>float<br>double<br>decimal<br>boolean<br>uuid<br>string<br>char<br>varchar<br>longtext<br>alphanumeric<br>email<br>url<br>username<br>password<br>phone<br>address<br>city<br>state<br>country<br>zip<br>ipv4<br>ipv6<br>mac_address<br>company<br>company_suffix<br>color<br>hexcolor<br>date<br>time<br>datetime<br>future_date<br>past_date<br>credit_card<br>currency<br>iban<br>bic<br>job_title</pre><p><strong>Custom (String | Number, etc.):</strong></p><ul><li>When fake is set to false, this field specifies a fixed value for the column.</li></ul><p><strong>Custom Object for Foreign Key:</strong></p><ul><li>For example, in the context_id(or any column you designate) field, instead of manually setting a number or generating a fake value, you can use an object with a reference_table key. This instructs the seeder to &quot;look up a value for this column from another table.&quot;</li><li>In this case, it will retrieve an id from the sites table.</li></ul><p><strong>Maintaining Referential Integrity:</strong></p><ul><li>This approach ensures that the value inserted into the context_id (or any column you designate) is an existing valid key from the sites table.</li><li>It is especially useful for foreign key relationships, as it prevents the need to hardcode or guess the correct value.</li></ul><p><strong>Different Behavior for Each Field (Example: </strong><strong>context_id):</strong></p><ul><li><strong>fake: false</strong> – No fake value is generated.</li><li><strong>custom</strong> – The value is obtained by referencing the actual id from the sites table.</li></ul><p><strong>Custom for Add Self Table Column value ( {column_name} ):</strong></p><p>The &quot;custom&quot; key is used to assign a fixed or computed value to a column instead of generating a fake one. In this case, when you set:</p><p>you’re using a self‑reference marker. This marker tells the seeder logic that the value for this column should come from the already-generated (or provided) value of another column — in this example, the &quot;name&quot; column.</p><p><strong>Marker Detection:</strong><br>When the seeder processes the factory , it checks if the custom value matches a pattern like &quot;{other_column}&quot;. If it does, the value isn’t immediately manipulated (e.g., by fake data generation or regex replacement) but is saved as a marker.</p><p><strong>Convert Case (“convert_case” : “lower”) :</strong></p><p>This key help to column convert value into <strong>lower/upper/capitalize</strong> case.</p><p><strong>Manipulation:</strong></p><p>in this configuration, the &quot;manipulation&quot; property is used to modify the column&#39;s value by applying a regular expression transformation. Here&#39;s what it does in your example:</p><ul><li><strong>Regex Pattern (</strong><strong>&quot;regex&quot;: &quot;\\s&quot;):</strong><br> This pattern matches any whitespace character in the string.</li><li><strong>Replacement String (</strong><strong>&quot;replace_with&quot;: &quot;-&quot;):</strong><br> When the regex finds a match (i.e., a space), it replaces it with a hyphen (-).</li><li><strong>Purpose in Context:</strong><br> For the &quot;name&quot; column, even if the value is generated (e.g., via a fake data generator or provided as custom input), the value will be post-processed to replace all spaces with hyphens. So if the value was &quot;John Doe&quot;, after manipulation it would become &quot;John-Doe&quot;</li></ul><p>This is not the final release — new features will be added in future versions! Stay updated by visiting <a href="https://dohrnyx.com/">Dohrnyx</a>, creating an account, and exploring our useful products and services. 🚀</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p0jT8I-PpacWJPcTgMZBKg.jpeg" /><figcaption>Dohrnyx Services Private Limited</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RCMET7dBSWhw5IUpW6rwVg.jpeg" /><figcaption>Dohrnyx</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*9V2dU9GLLwJQmgpQ7py2eg.png" /><figcaption><a href="https://www.npmjs.com/package/migration-seeder-factory">Migration, Seeder and Factory Creator In Nodejs</a></figcaption></figure><p>Thank You for supporting us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07669929023a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>