Hi friends, i'm working in crud with vuejs, using vue-table, vue-strap for use modal, vue-validator and vue-editable (very simple component. Is better modify for best features).

Features:

• Search
• Add 1, with validation in client and server (need map laravel rules names with vue validator rules names
• Add 2
• Modal and edit
• Modal and edit 2
• Delete
• Edit in place
• Show and Hidden columns.
• Paginate and paginate styles.

I like any docs for add this to generator, i can overwrite templates, but doesn't the better option. I like pass --vuejs or --vue option for generate crud with this.

New files:

• crud.js
• model-config.js (this file is a file for each index -model- page, for config)
• modal folder with modal template files for each model. Folder and files
• Overwrite ApiRequest or create new extend from them, with this code:

    public function response(array $errors)
    {
        return Response::json(static::makeError($errors), 400);
    }

    /**
     * @param string $errors
     * @param array  $data
     *
     * @return array
     */
    public static function makeError($errors, array $data = [])
    {
        $res = [
            'success' => false,
            'errors' => $errors,
        ];

        if (!empty($data)) {
            $res['data'] = $data;
        }

        return $res;
    } 

• index action in ApiController for each model:

public function index(Request $request)
    {

        // handle sort option
        if (request()->has('sort')) {
            list($sortCol, $sortDir) = explode('|', request()->sort);
            $query = Provider::orderBy($sortCol, $sortDir);
        } else {
            $query = Provider::orderBy('name', 'asc');
        }

        if ($request->exists('filter')) {
            $query->where(function($q) use($request) {
                $value = "%{$request->filter}%";
                $q->where('name', 'like', $value)
                    ->orWhere('email', 'like', $value)
                    ->orWhere('code', 'like', $value);
            });
        }

        $perPage = request()->has('per_page') ? (int) request()->per_page : null;
        return response()->json($query->paginate($perPage));
    }

The scaffold generator does not allow a model to be updated if it contains a unique field.

For example field a is unique, field b is not. If i update field b it will not save.

Would be good relations can be assigned by command or json!

Maybe:

php artisan infyom:scaffold Post --relations="hasMany(Comment), belongsTo(User)"

Or

php artisan infyom:scaffold Post --hasMany=Comment --belongsTo=User

I'm new to laravel-generator. I created a simple project following the documentation instructions. This is my project setup with dependencies versions.

"require": { "php": ">=7.1.3", "fideloper/proxy": "~4.0", "infyomlabs/adminlte-templates": "5.6.x-dev", "infyomlabs/laravel-generator": "5.6.x-dev", "laravel/framework": "5.6.*", "laravel/tinker": "~1.0", "laravelcollective/html": "5.6.0" },

After running scaffold for a simple model I keep receiving AppBaseController' not found in the generated controller.

These are the steps to reproduce.

php artisan infyom:scaffold Project --fieldsFile=fields_projects.json php artisan migrate

fields_projects.json looks like this.

[
    {
        "name": "id",
        "dbType": "increments",
        "htmlType": "",
        "validations": "",
        "searchable": false,
        "fillable": false,
        "primary": true,
        "inForm": false,
        "inIndex": false
    },
    {
        "name": "title",
        "dbType": "string",
        "htmlType": "text",
        "validations": "required",
        "searchable": true
    },
    {
        "name": "body",
        "dbType": "text",
        "htmlType": "textarea"
    }
]

serve the app php artisan serve

go to http://127.0.0.1:8000/projects

get this error:

Symfony \ Component \ Debug \ Exception \ FatalErrorException (E_UNKNOWN) Class 'App\Http\Controllers\AppBaseController' not found

I've checked previous related issues here in the repository and tried different suggestions, but none could fix it. It seems I m missing something obvious here. Maybe others might be facing the same issue.

I am trying to generate model swagger docs, and I found that final model file has error . then I figure out that $template = get_template('model.model', 'swagger-generator'); will get the model.model from the /resources/infyom/infyom-generator-templates/model/model.stub
and I think this is big error

Hello bro, maybe add option for implement datatable javascript plugin for index page. For laravel exists some packages for this job. This is one: https://github.com/yajra/laravel-datatables.

Greets.

Hello, I want to list my records with datatables. step 1: add_on.datatabled = true step 2: executed the command php artisan infyom:api_scaffold Product

But when I checked in the admin panel after adding a product it is not showing data with datatables.

Am I missing something?

Regards, Saneesh

Firstly thank you so much for your wonderful software.

I'm having a lot of problems when attempting to generate scaffolding for anything that contains any type of field other than plain strings or numbers. I've tried all kinds of versions, both the boilerplates and installing into a fresh Laravel 5.2 install as per the instructions on your website.

Are date and boolean field types supposed to be working at this point in time, because they really are not.

For example, when creating a scaffold for a model that includes a date, the scaffolding is created, and allows me to create a record which includes a date. This record is then correctly displayed in the index, but when I attempt to edit this record, the existing date information is not placed into the date field. It just shows "dd/mm/yyyy" again.

If I include a boolean field with a checkbox, there is no display of that field in the index, and when editing the record, the box is show, but it's always checked, no matter what the existing record is. If I save the record with the box unchecked, then I can see by looking at the database directly that the record is not changed.

I'd appreciate knowing if these are know issues, so that I can stop trying to solve problems that I'm not creating.

Thank you so much for your help.

This is probably an extremely stupid question, but I'm still kinda new at this so go easy on me.

Let's say I have two tables "Productions" and "Tours" with the corresponding models and relationships all working fine and correct. The Productions table has 2 columns: ID and Title. The Tours table has a column called "production_id" which references the ID column in the Productions table, and it has its own ID as well as its own Title column.

The relationships go: a production has many tours and a tour has one production. I've used the php artisan infyom:scaffold $MODEL_NAME --fromTable --tableName=$TABLE_NAME commands to create the necessary repositories, etc.

When I go to the "tours/create" admin page, how would I get it to populate the "Production" field so that while it would show the title of the production on the web interface, in the background it's using the production's ID number and will let me save the new Tour?

Hi, I am using the CLI generator fieldsFile method. When I have less than 3 fields in the file, the artisan command give me 'There isn not input fields to generate.'

Hereby I attach my fieldsFile content.

[
    {
        "name": "id",
        "dbType": "increments",
        "htmlType": "",
        "validations": "",
        "searchable": false,
        "fillable": false,
        "primary": true,
        "inForm": false,
        "inIndex": false
    },
    {
        "name": "origin",
        "dbType": "string",
        "htmlType": "text",
        "validations": "required:unique",
        "searchable": true,
        "fillable": true,
        "primary": false,
        "inForm": true,
        "inIndex": false
    },
    {
        "name": "sequence",
        "dbType": "integer:unsigned",
        "htmlType": "select",
        "searchable": false,
        "fillable": true,
        "primary": false,
        "inForm": true,
        "inIndex": false
    }
]

Hello

I just setup laravel-generator with api_prefix = 'api' and api_version = 'v1'. But when I run php artisan infyom:api_scaffold Test the TestAPIController is placed directly in app/Http/Controllers/API/ without separate namespace for each version, and also the route registed by the package is not has v1 prefix too.

I this normal or it's has something to do with my configuration?

Thank you

When database_seeder option is set to true in config/laravel_generator.php, the seeder for model gets generated, but not called in database/seeders/DatabaseSeeder.php, which is expected.

Suggestion

After generating seeder, add a call to the seeder inside this->call([])' in DatabaseSeeder.php file. Create the call function if it does not exist already.

Looking at what gets generated in the Model file, I noticed 3 errors.

1. Double semi-colon

Here are the first 6 lines from Model file

<?php

namespace App\Models;

use Illuminate\Database\Eloquent\Model;
 use Illuminate\Database\Eloquent\SoftDeletes;; use Illuminate\Database\Eloquent\Factories\HasFactory;;

The 2nd and 3rd imports have repeated semi-colons at the end.

2. Incorrect spacing and new lines in top section

In the code block above we can also see some white space added before the keyword use, which should not be there.

We also see that two use statements are in the same line, which is incorrect and inconsistent with every other generated file, the white space before the second use should be replaced with \n.

Another \n should be added right after the second use statement, there is no new line between it and the line below (not an import).

3. Incorrect use of tabs inside model class

Here are the first few lines in the generated model class

 */class User extends Model
{
     use SoftDeletes;    use HasFactory;    public $table = 'users';

    public $fillable = [

Firstly, we can see there should be a \n before the class keyword, which is not present.

Secondly: the first 3 statements in the class are present on the same line, with tabs in place of new lines.

Thirdly: the aforementioned statements have white space before them that should not be present, clearly visible on use SoftDeletes;

Add an option to generate a policy file in config/laravel_generator.php, like this:

return = [
    ...
    'policy' => true
    ...
]

Assuming we are generating a model named Post, setting this option to true should:

1. Generate a PostPolicy file.
2. Register the policy in app/Providers/AuthServiceProvider.php
3. Implement Policy inside controller via user model

Caveat: policy must be implemented via user model, as implementing via controller helpers or via middleware both require implementation of route model binding, which cannot be applied when using repository pattern.

Suggestion: It's possible to use any of the 3 patterns when 'repository_pattern' => false, so another option might be generating different code depending on the value of repository_pattern config.

Assuming laravel_generator.php:

return = [
  ...
  'repository_pattern' => false,
  'resources' => false,
  ...
]

And assuming we are generating a model named Post, here's what gets generated in PostController.php:

  // code

  public function show($id): JsonResponse
  {
      /** @var Post $post */
      $post = Post::find($id);

      if (empty($post)) {
          return $this->sendError(
              __('messages.not_found', ['model' => __('models/post.singular')])
          );
      }

      return $this->sendResponse(
          $post->toArray(),
          __('messages.retrieved', ['model' => __('models/post.singular')])
      );
  }

  // code

This does not implement route model binding, which is a sane default in any project with policies. For example, this pattern is required if the developer wishes to implement policies via middleware or via controller helpers.

My suggestion is to generate code similar to this:

  // code

  public function show(Post $post): JsonResponse
  {
      if (empty($post)) {
          return $this->sendError(
              __('messages.not_found', ['model' => __('models/post.singular')])
          );
      }

      return $this->sendResponse(
          $post->toArray(),
          __('messages.retrieved', ['model' => __('models/post.singular')])
      );
  }

  // code

This returns identical results, while helping implement policies out of the box.

The caveat is that it's not a sane default when using the repository pattern, so this should only apply when that option is set to false.

When I create a Scaffold "php artisan infyom:api_scaffold Country --relations" like this or "php artisan infyom:api_scaffold Country" this command using foreign key relation to other table, then Not showing any data in dropdown. check the image

v5.4.1 Some rules are generated, but not every time (max:) ? Why does it not always appear for string field. All rules can be get from Doctrine\DBAL\Schema\AbstractSchemaManager, $details = $this->schemaManager->listTableDetails($this->tableName); which will always tell you the string length:

In this case string length is 10 so we should have max:10 but this does not appear in models $rules 'account' => 'required|string', Some fields do have it, but I think it should always be put in string type field rules.