Migration file maintenance

[thaarrtt]

I wrote my migration like below example, I feel like this is better because. it does grouping and make it more maintainable

I just asking if this is okay, and is there a better way to manage this thing

pub struct Migrator;

#[async_trait::async_trait]
impl MigratorTrait for Migrator {
    fn migrations() -> Vec<Box<dyn MigrationTrait>> {
        // Collect migrations into a single vector
        let mut migrations = Vec::new();

        // Add user schema migrations
        migrations.extend(user_schema_migrations());

        // Add catalog schema migrations
        migrations.extend(catalog_schema_migrations());

        migrations
    }
}

// User Schema Migrations
fn user_schema_migrations() -> Vec<Box<dyn MigrationTrait>> {
    vec![
        // Core Infrastructure
        Box::new(m20241118_234209_create_extension::Migration),
        Box::new(m20241118_234435_create_enum::Migration),
        // User and Authentication Related
        Box::new(m20241118_234533_create_user_table::Migration),
        // Financial Infrastructure
        Box::new(m20241118_234629_create_wallet_account::Migration),
        Box::new(m20241118_234701_transaction::Migration),
        Box::new(m20241118_234740_create_ledger_entries::Migration),
        Box::new(m20241118_234921_create_journal_entries::Migration),
        // System Triggers and Utilities
        Box::new(m20241127_205444_create_trigger::Migration),
    ]
}

// Catalog Schema Migrations
fn catalog_schema_migrations() -> Vec<Box<dyn MigrationTrait>> {
    vec![
        // Catalog Schema Foundation
        Box::new(m20241204_151847_create_catalog_schema::Migration),
        // Supplier and Product Migrations
        Box::new(m20241204_152404_catalog_supplier_product::Migration),
        Box::new(m20241204_152518_catalog_supplier_order::Migration),
        Box::new(m20241204_152558_catalog_supplier_order_items::Migration),
    ]
}