/ 
Mojolicious-Command-generate-resources-0.05
River stage zero No dependents
/ Mojolicious::Command::generate::resources

NAME

Mojolicious::Command::generate::resources - Resources from database for your application

SYNOPSIS

Usage: APPLICATION generate resources [OPTIONS]

  my_app.pl generate help resources # help with all available options
  my_app.pl generate resources --tables users,groups

DESCRIPTION

This is an early release. Mojolicious::Command::generate::resources generates directory structure for a fully functional MVC set of files, and routes based on existing tables in your application's database.

This tool's purpose is to promote RAD by generating the boilerplate code for model (M), templates (V) and controller (C) and help programmers to quickly create well structured, fully functional applications. It assumes that you already have tables created in a database and you just want to generate CRUD actions for them.

In the generated actions you will find eventually working code for reading, creating, updating and deleting records from the tables you specified on the command-line. The generated code is just boilerplate to give you a jump start, so you can concentrate on writing your business-specific code. It is assumed that you will modify the generated code to suit your specific needs. All the generated code is produced from templates which you also can put in your application renderer's path and modify to your taste.

The command expects to find and will use one of the commonly used helpers pg, mysql sqlite. The supported wrappers are respectively Mojo::Pg, Mojo::mysql and Mojo::SQLite.

OPTIONS

Below are the options this command accepts, described in Getopt::Long notation. Both short and long variants are shown as well as the types of values they accept. All of them, beside --tables, are guessed from your application and usually do not need to be specified.

C|controller_namespace=s

Optional. The namespace for the controller classes to be generated. Defaults to app->routes->namespaces->[0], usually MyApp::Controller, where MyApp is the name of your application. If you decide to use another namespace for the controllers, do not forget to add it to the list app->routes->namespaces in myapp.conf or your plugin configuration file. Here is an example.

# Setting the Controller class from which all controllers must inherit.
# See /perldoc/Mojolicious/#controller_class
# See /perldoc/Mojolicious/Guides/Growing#Controller-class
app->controller_class('MyApp::C');

# Namespace(s) to load controllers from
# See /perldoc/Mojolicious#routes
app->routes->namespaces(['MyApp::C']);

H|home_dir=s

Optional. Defaults to app->home (which is MyApp home directory). Used to set the root directory to which the files will be dumped.

L|lib=s

Optional. Defaults to app->home/lib (relative to the --home_dir directory). If you installed MyApp in some custom path and you wish to generate your controllers into e.g. site_lib, set this option.

M|model_namespace=s

Optional. The namespace for the model classes to be generated. Defaults to MyApp::Model.

T|templates_root=s

Optional. Defaults to app->renderer->paths->[0]. This is usually app->home/templates directory. If you want to use another directory, do not forget to add it to the app->renderer->paths list in your configuration file. Here is how to add a new directory to app->renderer->paths in myapp.conf.

# Application/site specific templates
# See /perldoc/Mojolicious/Renderer#paths
unshift @{app->renderer->paths}, $home->rel_file('site_templates');

t|tables=s@

Mandatory. List of tables separated by commas for which controllers should be generated.

SUPPORT

Please report bugs, contribute and make merge requests on Github.

ATTRIBUTES

Mojolicious::Command::generate::resources inherits all attributes from Mojolicious::Command and implements the following new ones.

args

Used for storing arguments from the commandline template.

my $args = $self->args;

description

my $description = $command->description;
$command        = $command->description('Foo!');

Short description of this command, used for the commands list.

routes

$self->routes();

Returns an ARRAY reference containing routes, prepared after $self->args->{tables}. Suggested Perl code for the routes is dumped in a file named TODO in --homedir so you can copy and paste into your application code.

usage

my $usage = $command->usage;
$command  = $command->usage('Foo!');

Usage information for this command, used for the help screen.

METHODS

Mojolicious::Command::generate::resources inherits all methods from Mojolicious::Command and implements the following new ones.

run

Mojolicious::Command::generate::resources->new(app=>$app)->run(@ARGV);

Run this command.

TODO

The work on the features may not go in the same order specified here. Some parts may be fully implemented while others may be left for later.

- Improve documentation. Tests.
- Tests for templates (views).
- Tests for model classes.
- Test the generated routes.
- Implement generation of Open API specification out from
  tables' metadata. More tests.

AUTHOR

Красимир Беров
CPAN ID: BEROV
berov@cpan.org
http://i-can.eu

COPYRIGHT

This program is free software licensed under

Artistic License 2.0

The full text of the license can be found in the LICENSE file included with this module.

SEE ALSO

Mojolicious::Command::generate, Mojolicious::Command, Mojolicious, Perl.