masterrecord 0.3.12 → 0.3.13

package/Migrations/cli.js

@@ -58,15 +58,15 @@ program.option('-V', 'output the version');
         // location of folder where command is being executed..
         var executedLocation = process.cwd();
         // find context file from main folder location
-        var contextInstance = migration.findContext(executedLocation, contextFileName);
-        if(!contextInstance){
+        var contextFile = migration.findContextFile(executedLocation, contextFileName);
+        if(!contextFile){
           console.error(`\n❌ Error - Cannot read or find Context file '${contextFileName}.js'`);
           console.error(`\nSearched in: ${executedLocation}`);
           console.error(`\nMake sure your Context file exists and is named correctly.`);
           return;
         }
         var snap = {
-          file : contextInstance.fileLocation,
+          file : contextFile,
           executedLocation : executedLocation,
           contextEntities : [],
           contextFileName: contextFileName.toLowerCase()

package/Migrations/migrations.js

@@ -166,6 +166,16 @@ class Migrations{
 
 
 
+    findContextFile(executedLocation, contextFileName){
+        var files = globSearch.sync(`**/*${contextFileName}.js`, {
+            cwd: executedLocation,
+            dot: true,
+            windowsPathsNoEscape: true
+        });
+        var file = files && files[0] ? path.resolve(executedLocation, files[0]) : null;
+        return file;
+    }
+
     findContext(executedLocation, contextFileName){
         var files = globSearch.sync(`**/*${contextFileName}.js`, {
             cwd: executedLocation,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "masterrecord",
-  "version": "0.3.12",
+  "version": "0.3.13",
   "description": "An Object-relational mapping for the Master framework. Master Record connects classes to relational database tables to establish a database with almost zero-configuration ",
   "main": "MasterRecord.js",
   "bin": {

package/readme.md

@@ -1640,10 +1640,27 @@ MasterRecord has been upgraded to meet **FAANG engineering standards** (Google/M
 - ✅ **Duplicate db/migrations Path Fixed** - Resolved bug where snapshot files were created with duplicate nested paths
   - **Before**: `/components/qa/app/models/db/migrations/db/migrations/qacontext_contextSnapShot.json` ❌
   - **After**: `/components/qa/app/models/db/migrations/qacontext_contextSnapShot.json` ✅
+  - **Root Cause**: Incorrect glob API usage in `findContext` method (migrations.js:169-181)
+  - **Fix**: Changed to use relative pattern + options object + `path.resolve()` for guaranteed absolute paths
 - ✅ **Smart Path Resolution** - Added `pathUtils.js` with intelligent path detection
 - ✅ **Prevents update-database-restart Failures** - Snapshot files now always created in the correct location
 - ✅ **Cross-Platform Support** - Works correctly on Windows and Unix-based systems
 
+**Running Migrations - Important Notes:**
+- **Don't move migration files** - Leave them in their generated location (e.g., `/components/qa/db/migrations/`)
+- **Two ways to run migrations:**
+  1. **From anywhere** - Run MasterRecord CLI from your project root, it will find migrations automatically:
+     ```bash
+     npx masterrecord enable-migrations components/qa/app/models/qaContext
+     npx masterrecord update-database components/qa/app/models/qaContext
+     ```
+  2. **From migration directory** - cd into the specific migration area and run CLI there:
+     ```bash
+     cd components/qa/db/migrations
+     npx masterrecord update-database ../../app/models/qaContext
+     ```
+- MasterRecord uses intelligent path resolution to locate migrations regardless of where you run the command
+
 ### Core Improvements (context.js)
 
 **Critical Fixes:**