fix(*): adding two more members to be migrated

Author: kdinev

projects/igniteui-angular/migrations/update-21_0_0/index.ts

@@ -383,6 +383,8 @@ const ENTRY_POINT_MAP = new Map<string, string>([
     ['IgxGridFooterComponent', 'grids/core'],
     ['IgxColumnLayoutComponent', 'grids/core'],
     ['IgxExporterEvent', 'grids/core'],
+    ['IGridEditDoneEventArgs', 'grids/core'],
+    ['IgxGridRow', 'grids/core'],
     ['IgxGridEditingActions', 'grids/core'], // Grid actions moved to grids
     ['IgxGridPinningActions', 'grids/core'], // Grid actions moved to grids
     ['IgxGridActionButtonComponent', 'grids/core'], // Grid actions moved to grids
@@ -802,7 +804,7 @@ export default function migrate(options: MigrationOptions): Rule {
         context.logger.info(`Applying migration for Ignite UI for Angular to version ${version}`);
 
         const update = new UpdateChanges(__dirname, host, context);
-        const shouldMigrateImports = options.migrateImports !== false; // Default to true if not specified
+        const shouldMigrateImports = options.migrateImports === true;
 
         if (shouldMigrateImports) {
             context.logger.info('Migrating imports to new entry points...');

projects/igniteui-angular/migrations/update-21_0_0/schema.json

@@ -7,8 +7,11 @@
     "migrateImports": {
       "type": "boolean",
       "description": "Migrate imports to use granular entry points (e.g., 'igniteui-angular/grids' instead of 'igniteui-angular'). The library remains backwards compatible - you can continue using the main entry point.",
-      "default": true,
-      "x-prompt": "Would you like to migrate your imports to use the new granular entry points for better tree-shaking? (The library remains backwards compatible if you choose 'No')"
+      "x-prompt": {
+        "message": "Would you like to migrate your imports to use the new granular entry points for better tree-shaking?",
+        "type": "confirmation"
+      }
     }
-  }
+  },
+  "required": ["migrateImports"]
 }