• Added --pagination option to the crud:generate and crud:controller options to change amount of models shown per page on index page, e.g. crud:generate --fields="...." --pagination=50
• added --indexes option (see #102) e.g. crud:generate --fields="title#string,some_value#integer" --indexes="some_value" which will result in a migration of $table->index('some_value');. You can also do --indexes="some_value#unique" which will result in $table->unique('some_value');.
• added --required-fields option to allow for required fields to be specified (this means it's now ignoring any #req or #required that may be defined in the fields string. This helps make the crud definition easier to write and understand. e.g. crud:generate --fields="title#string,value#integer" --required-fields="title". Fields that are not required will be set to nullable
• added --foreign-keys option to migration and generate command. This will create references in the migration table only, and won't create any relationship functions in the model class - that will come next! e.g. --foreign-keys="owner_id#id#owners" where owner_id is the field name of the current table, id is the id column name on the related table, and owners is the related table name.
• added --relationships option to auto-create relationship methods. This will create the necessary functions in the model class for relationships. Use; --relationships="relationshipName#relationshipType#argsSeparatedByPipes" where relationshipType is hasOne, belongsTo etc. User is responsible for ensuring the relationship is valid. The args will be split by pipe, and fed into the function. e.g. --relationships="owner#hasOne#App\Owner" This will create the function owner(){$this->hasOne('App\Owner');}. Notice that for each arg in the third section, single quotes will be wrapped around the string.
• in crud:generate, changed --namespace argument to controller-namespace and also added a model-namespace for models
• updated readme.md
• pagination now uses 25 as the default instead of 15
• added --form-validation option for specifying details of form validation for the html form. e.g. --form-validation="title#required|min:2|max:20,description#max:250

Message: Too many arguments, expected arguments "command" "name".

Command: php artisan crud:generate Fornecedores --fields_from_file="/resources/crudGenerator/fornecedorFields" --view-path=admin --controller-namespace=Admin --route-group=admin form-helper=html

My .json { "fields": [ { "name": "razao_social", "type": "string" }, { "name": "cnpj", "type": "text" }, { "name": "estado", "type": "select", "options": { "AC": "Acre", "AL": "Alagoas", "AP": "Amapá", "AM": "Amazonas", "BA": "Bahia", "CE": "Ceará", "DF": "Distrito Federal", "ES": "Espírito Santo", "GO": "Goiás", "MA": "Maranhão", "MT": "Mato Grosso", "MS": "Mato Grosso do Sul", "MG": "Minas Gerais", "PA": "Pará", "PB": "Paraíba", "PR": "Paraná", "PE": "Pernambuco", "PI": "Piauí", "RJ": "Rio de Janeiro", "RN": "Rio Grande do Norte", "RS": "Rio Grande do Sul", "RO": "Rondônia", "RR": "Roraima", "SC": "Santa Catarina", "SP": "São Paulo", "SE": "Sergipe", "TO": "Tocantins" } }, { "name": "cidade", "type": "text" }, { "name": "logradouro", "type": "select", "options": { "avenida": "Avenida", "alameda": "Alameda", "beco": "Beco", "rua": "Rua", "travessa": "Travessa", "viela": "Viela" } }, { "name": "complemento", "type": "text" }, { "name": "cep", "type": "text" }, { "name": "tel1", "type": "text" }, { "name": "tel2", "type": "text" }, { "name": "email", "type": "text" }, { "name": "responsavel", "type": "text" }, { "name": "user_id", "type": "integer#unsigned" } ], "validations": [ { "field": "responsavel", "rules": "required|max:15" }, { "field": "razao_social", "rules": "required|max:15" },{ "field": "email", "rules": "required|max:30" },{ "field": "complemento", "rules": "required|max:30" } ] }

What the problem? Thankyou.

A few enhancements - happy to do PR's but want to make sure it lines up to your vision first.

One

At the moment it feels very much like a one use tool (it is a generator, so makes sense) - you run the generator, it creates everything and thats that. In reality though, I frequently add, modify and otherwise change models, migrations, etc.

It would be good if this tool could account for that - much like Django's admin feature. There are a core set of models (this would be somewhat similar to your .json definitions), and from that everything is generated. The difference being that you can make updates to those core definitions and re-run the command and everything will update.

If you do that with crud-generator it:

• Doesn't update the controller
• Doesn't update the model
• Creates a new migration (so you end up with multiple migrations)
• Updates the view

So already, there are 3 possible outcomes (a "no update", a "new" and a "replace"). I understand not updating, but if that is desired, it should be the same for all.

Ideally though, running update (possibly with a --force) would re-generate everything.

So based on this - using models, possibly with some form of annotations instead of the .json would facilitate this. That way a user can update their models (and act as the source of truth), and migrations, controllers, and views are generated.

Two

A lot of awkward functionality is introduced by trying to get the CrudCommand to call the subcommands (joining relationships on '#' then splitting them back out). I suggest that you seperate out a set of service classes - one for each each command. Eg. CrudControllerService. In turn both CrudCommand and CrudControllerCommand invoke CrudControllerService, instead of CrudCommand trying to communicate directly with CrudControllerCommand via strings in the command line.

Three

And... this leads on to the third - relationships. It would be nice to start to introduce relationships (see attached image). Starting with belongsTo would be a good start - where instead of typing the id of the related model, a drop down would be used.

I've tried to tackle this, but the passing relationship strings along the command line is becoming unweirdly (hence the request for the second feature above (services)).

Four

Finally :) - How do you feel about using blade instead of the manual string replaces everywhere? For example:

The image is just really basic sample stuff - but it would really clean up the generators by not having to have str_replace everywhere.

[Symfony\Component\Console\Exception\CommandNotFoundException]
There are no commands defined in the "crud" namespace.

When I run the generator. I ran the composer require and update, and updated my app.config file with the right providers and aliases.

I also ran php artisan vendor:publish

Any ideas

I rewrote everything to be able to use this plugin without the form helper. All fields have been replaced by normal fields and I used old() and isset() on variables in the edit field to maintain the form-model binding functionality

After passing the CRUD command : php artisan crud:generate Posts --fields='title#string; content#text; category#select#options={"technology": "Technology", "tips": "Tips", "health": "Health"}' --view-path=admin --controller-namespace=Admin --route-group=admin --form-helper=html

I have the following error: Too many arguments expected arguments "command" "name".

what does mean and what I should do to fix this error?

The current views generated for file inputs don't facilitate arrays of file uploads, and so the handling of the file data can be greatly simplified (currently, when its treated as an array, its not working at all).

Secondly, updated to use Laravel's built in store method as well as the built in hashName() method - this will make it far more consistent with how other files are uploaded

Future enhancements would include the migrations for files creating multiple fields (original file name, path, mimetype, etc).

I am facing one problem, if you can suggest some solution. As mentioned on the home page, under Options sections, there are 2 options for localize and locales. I have used it but I did not see its working. May be I did something wrong. Can you please suggest how to make it work. I am using two languages english(ltr) and arabic(rtl).

It'd be awesome if you could specify a namespace for the model being generated. So far I've only been able to get them generated at App\SomeModel.php. A flag like --model-namespace=Models/Front/Blog that creates the model in that location. Otherwise, you need to move the model then edit its' templates and the controller to reference the new namespace.

I constantly use CrudGenerator for my packages and am always copying/pasting in a common config file. This would make config generation part of the crudgenerator process.

more of a note to myself, which I'll implement soon: e.g.:

--pk="field1|field2" primary key on field1 and field2 --indexes="field1|field2,field3" composite index on field1 and field2, and another separate index on field3

Hi. Thanks for this very useful package. I believe that using the route() helper instead of url() would simplify a lot the templates. In principle I could use the route names instead the prefix, but because you append a / to the routeGroup option I have to modify the templates manually after I generate them. If you don't have time for this modification I could make a pull request when I can.

Hi, I really like this generator. Then a create a fork and add my preferences to this:

• Change

<td>{{ $loop->iteration }}</td>

to

<td>{{ $item->id }}</td>

in src/stubs/views/html/index.blade.stub

• Change

<table class="table">

to

<table class="table table-sm">

in src/stubs/views/html/index.blade.stub

• Add orderBy() to controller
• Add folder includes in publish/views
• and others

I believe a feature to purge or rollback the changes is needed.

Can you work on something like crud:rollback --tag=blog Also, add a feature to tag crud:generate command so to rollback.