README

LeanOrm Cli

About

This is a simple command line tool for creating LeanOrm Collection, Model & Record classes for each table & view in a specified database. This tool reads information about tables and views from the db & uses that information to generate the desired earlier mentioned classes.

Installation

composer require --dev rotexsoft/leanorm-cli

Usage

Create model, record & collection classes for all tables & views using the specified config

php ./vendor/bin/generate-leanorm-classes.php /path/to/config.php

Create model, record & collection classes for a specified table or view using the specified config
- Replace table_or_view_name with the name of the table or view you want to generate classes for

php ./vendor/bin/generate-leanorm-classes.php /path/to/config.php table_or_view_name

You need to create a config file that will be passed to the command above. This config file must return an array with the minimum structure below:

return [
    'pdo' => [             // An array with a minimum of 1 item and a maximum of 4 items or an instance of the PDO class
        'sqlite::memory:', // 1st compulsory item is a dsn string to be passed as 1st arg to the PDO consructor
        'username',        // 2nd optional item is a username string to be passed as 2nd arg to the PDO consructor
        'password',        // 3rd optional item is a password string to be passed as 3rd arg to the PDO consructor
        [],                // 4th optional item is an options array to be passed as 4th arg to the PDO consructor
    ],                                                              
    
    'namespace' => null,              // Root Namespace classes will belong to. E.g. 'App\\DataSource'. Null means no namespace.
    'directory' => './model-classes', // Absolute or relative path to where classes are to be written
];

See sample-config.php for the full structure of the array that should be returned by the config file. Each item in the sample config file is thoroughly described & you can specify the ones you want in your own config file.

Note: running the command multiple times will not lead to all previously generated classes being overwritten. The only files that get overwritten would be the ones ending with FieldsMetadata.php. If you want all classes to be regenerated, you would have to manually delete them before re-running the command.

Note: when you modify table or view columns in your database and you have previously generated your classes using a config whose store_table_col_metadata_array_in_file entry has a value of true, you SHOULD re-run this tool with the same config to update all the table column metadata files (i.e. those ending with FieldsMetadata.php) so that your table / view column modifications are reflected in your application. This re-run will not modify your Model, Record & collection class files.

The classes generated will have the directory structure below for a database with an authors table & a posts table:

/path
    /where
        /classes
            /were
                /written
                |_________Authors
                |           |______AuthorsCollection.php     # Collection class for the authors table
                |           |______AuthorsModel.php          # Model class for the authors table 
                |           |______AuthorRecord.php          # Record class for the authors table 
                |           |______AuthorsFieldsMetadata.php # Metadata array for the authors table columns, ONLY generated when the config entry **store_table_col_metadata_array_in_file** has a value of **true**
                |
                |_________Posts
                            |______PostsCollection.php     # Collection class for the posts table
                            |______PostsModel.php          # Model class for the posts table 
                            |______PostRecord.php          # Record class for the posts table 
                            |______PostsFieldsMetadata.php # Metadata array for the posts table columns, ONLY generated when the config entry **store_table_col_metadata_array_in_file** has a value of **true**

Most of these classes will be empty, and are provided so you can extend their behavior if you wish. They also serve to assist IDEs with autocompletion of some typehints.

Custom Templates

You can override the templates used by this tool and provide your own instead. This lets you customize the code generation; for example, to add your own common methods or to extend intercessory classes.

The templates used by this tool are located here, you can look at them to have an idea of how to craft your custom templates. Your custom templates can be located in any directory / folder of your choosing but they must have the same names as the default template files, i.e:

TypesCollection.php.tpl
TypesModel.php.tpl
TypeRecord.php.tpl

You do not have to override all the template files, you can just override the ones you want to customize, the ones you do not override will keep using the default template(s). For example, you may only want to override the Model template TypesModel.php.tpl, which will lead to the default Collection & Record templates to continue being used for creating Collection & Record classes, while your custom Model template would be used for creating Model classes.

You will need to specify the directory containing your custom template files in the config file earlier described by adding an item with the key custom_templates_directory like so:

return [
    'pdo' => [             // An array with a minimum of 1 item and a maximum of 4 items
        'sqlite::memory:', // 1st compulsory item is a dsn string to be passed as 1st arg to the PDO consructor
        'username',        // 2nd optional item is a username string to be passed as 2nd arg to the PDO consructor
        'password',        // 3rd optional item is a password string to be passed as 3rd arg to the PDO consructor
        [],                // 4th optional item is an options array to be passed as 4th arg to the PDO consructor
    ],                                                              
    
    'namespace' => null,              // Root Namespace classes will belong to. E.g. 'App\\DataSource'. Null means no namespace.
    'directory' => './model-classes', // Absolute or relative path to where classes are to be written
    'custom_templates_directory' => './path', // Absolute / relative path to a location containing 1 or more template files below
                                              // TypesModel.php.tpl, TypesCollection.php.tpl & TypeRecord.php.tpl
];

Below is a full list of variables / tokens that are present in the template files:

{{{COLLECTION_EXTENDED}}} will be substituted with the fully qualified class name of the collection each new collection class will extend. Default is \LeanOrm\Model\Collection
{{{MODEL_EXTENDED}}} will be substituted with the fully qualified class name of the model each new model class will extend. Default is \LeanOrm\Model
{{{RECORD_EXTENDED}}} will be substituted with the fully qualified class name of the record each new record class will extend. Default is \LeanOrm\Model\Record
{{{CREATED_TIMESTAMP_COLUMN_NAME}}} will be substituted with NULL or name of the db column that will be timestamped each time a new record is inserted into the db
{{{UPDATED_TIMESTAMP_COLUMN_NAME}}} will be substituted with NULL or name of the db column that will be timestamped each time a record is saved to the db
{{{DB_COLS_AS_PHP_CLASS_PROPERTIES}}} will be substituted with a partial docblock of db field names for a Record
{{{NAME_SPACE}}} will be subsituted with an empty string or a specified namespace name with \{{{MODEL_OR_COLLECTION_CLASS_NAME_PREFIX}}} appended to it
{{{MODEL_OR_COLLECTION_CLASS_NAME_PREFIX}}} will be subsituted with a pluralized camel-cased version of {{{TABLE_NAME}}}
{{{RECORD_CLASS_NAME_PREFIX}}} will be subsituted with a singularized camel-cased version of {{{TABLE_NAME}}}
{{{PRIMARY_COL_NAME}}} will be subsituted with an empty string or the name of the primary key column in the table {{{TABLE_NAME}}}
{{{TABLE_NAME}}} will be subsituted with the name of the db table that we are generating collection, model & record classes for
{{{METADATA_ARRAY}}} will be subsituted with an array containing table col metadata which will be included in model constructors if the config entry store_table_col_metadata_array_in_file has a value of true
{{{INCLUDE_TABLE_COL_METADATA}}} will be subsituted with an include statement (including the metadata array) in the model classes' constructors if the config entry store_table_col_metadata_array_in_file has a value of true

Contributing

Running Tests

To run the tests in this package, just run the command below:

composer test

By default, the tests run against an in-memory sqlite database using PDO.

To change the tests to run against another database engine such as mysql, run the command below:

composer gen-test-pdo-config

Then go and edit ./tests/pdo.php with the PDO arguments for the database you want to connect to.

Note that you only need to point to a database that has been created. You don't have to create the tables and views needed for testing, they will automatically be created when the test suite is run. In fact make sure there are no views or tables in the configured database. Also make sure the username you specified (for non-sqlite DBs) has permission to create and drop tables and view.

Because of the way the test-suite is designed, in-memory sqlite does not work. The sqlite db must be stored in a file. This is already setup in the default pdo config.

The package should work with MS Sqlserver, but the tests will only run with sqlite, mysql & postgres databases.

rotexsoft / leanorm-cli

Maintainers

Details