cycle / schema-migrations-generator Goto Github PK

Successfully installed:

        "cycle/database": "2.3.0",
        "cycle/migrations": "4.0.1",
        "cycle/orm": "2.2.1",

Error when executing: composer require cycle/schema-migrations-generator

Problem 1
    - cycle/schema-migrations-generator 1.0.0 requires cycle/database ^1.0.2 -> found cycle/database[1.0.2, 1.0.3, 1.0.4] but it conflicts with your root composer.json require (^2.3).
    - cycle/schema-migrations-generator 2.0.0 requires cycle/migrations ^3.0 -> found cycle/migrations[v3.0.0, v3.1.0, v3.1.1] but it conflicts with your root composer.json require (^4.0).
    - Root composer.json requires cycle/schema-migrations-generator * -> satisfiable by cycle/schema-migrations-generator[1.0.0, 2.0.0].

Code also should be updated

In the current practice of creating database migrations, migration names are excessively long and contain unnecessary information, making them challenging to read, although still somewhat understandable. For example, the migration name 20230911.140854_0_0_default_change_asset_add_index_b59dda2670cd99c7e59d56efbcf42282_change_project_scan_alter_config_alter_input_change_asset_add_.php is quite burdensome to decipher.

Proposal

It is recommended to establish a convention where migration names primarily reflect the initial set of changes being made. Including the first couple of changes in the migration name should suffice to maintain clarity. For example, a migration name like 2022_05_20_090500_add_index_change_project_scan_in_asset_table.php conveys the primary purpose of the migration, making it more readable and comprehensible.

It appears only in tests and maybe doesn't require there

Should be researched and fixed: cycle/migrations#7