ascsoftw / tall-crud-generator Goto Github PK

I have installed this awesome package and I have run composer require laravel/ui command, then php artisan ui bootstrap --auth also

and I have followed the package steps, BUT in the Select Fields step as shown here

this issue triggered when I click NEXT

How I can solve this issue?

@locopine

Generated Code for Component with CamelCased Name like LaravelTips has been fixed in the latest release.

@ascsoftw

Great job! What I reported has indeed been corrected and is perfect.

By an oversight, when reporting on the last issue issue 9#, I ended up not reporting, also, that the same behavior happens in "$this->emitTo('LaravelTips', 'refrefh');". This causes the "index" not to update!

I corrected it, in my tests, as follows:

From

• $this->emitTo('LaravelTips', 'refrefh');
  To
• $this->emitTo('laravel-tips', 'refrefh');

In this way it worked well.

Thx.

everything was fine until when I tried to edit or delete the user or create a new user even, I found that the button action does NOT work!

Undefined index: belongsToMany (View: /Users/project/vendor/ascsoftw/tall-crud-generator/resources/views/livewire/step4.blade.php)

<x:tall-crud-generator::dialog-modal wire:model="confirmingBelongsToMany">

<x-slot name="title">

    Add a Belongs to Many Relationship

</x-slot>


<x-slot name="content">

    <div class="mt-4">

        <div>

            <x:tall-crud-generator::label>Select Relationship</x:tall-crud-generator::label>

            <x:tall-crud-generator::select class="block mt-1 w-1/2" wire:model.lazy="belongsToManyRelation.name">

                <option value="">-Please Select-</option>

                @foreach($allRelations['belongsToMany'] as $c)

                <option value="{{$c['name']}}">{{$c['name']}}</option>

                @endforeach

            </x:tall-crud-generator::select>

            @error('belongsToManyRelation.name') <x:tall-crud-generator::error-message>{{$message}}</x:tall-crud-generator::error-message> @enderror

        </div>

Hi,
Your generator is fun. While can override some styles, it would be fun to have better control concerning the styling. For example, your table stub has "text-xs" style in it, which is too small for my liking, or the blue style has to be changed in several fields. While it's ok to override one model, It can be cumbersome and subject to errors to change this on several models.

Keep up your good work!

I am getting errors after installing this package. I can't login.
I've published config and views but also same issue arise.
Help needed for error provided below: Thank you in advance.

InvalidArgumentException
Unable to locate class or view [tall-crud-generator::label] for component [label].

using Breeze,Tailwind,Livewire,Alpine !

We followed the steps as suggested in the documentation. Livewire, Tailwind css , Alpinejs are installed. Installed the crud generator.
Used @livewire('tall-crud-generator') in one of my blade file. But the design is completly broken and unable to proceed. Can you please check and respond as early as possible.

Using Laravel 10, Php 8.1

First - Awesome Tool! This is 'exactly' what I needed to get started with and Laravel Livewire Datatables.
This applies to v2.4.0.
Issue - This didn't automatically take into account the table name changes for tables with a prefix.
I had a suggestion that might be good to incorporate?
Try/catch block of tallCrudGenerator.php -> method checkModel
try {
$model = new $this->modelPath();
$this->modelProps['tableName'] = Schema::connection( $model->getConnectionName() )->getConnection()->getTablePrefix() . $model->getTable();
$this->modelProps['primaryKey'] = $model->getKeyName();
$this->modelProps['columns'] = $this->getColumns(Schema::connection( $model->getConnectionName() )->getColumnListing( $model->getTable() ), $this->modelProps['primaryKey']);
} catch (Exception $e) {
$this->addError('modelPath', 'Not a Valid Model Class.');
return;
}

Additionally - I love all of the options, but I found for myself that it was speedier to delete/uncheck or change things once I knew what was possible, other than the other way around, so a couple nice-to-haves or optional or maybe someone might find useful?

modifications:

tallCrudGenerator.php ->

    public $primaryKeyProps = [
        'inList' => true,
        'label' => 'ID',
        'sortable' => true,
    ];

    public function addField($column = '')
    {
        $this->fields[] = [
            'column' => $column,
            'label' => ucwords(implode(" ",explode("_",$column))),
            'sortable' => true,
            'searchable' => true,
            'inList' => true,
            'inAdd' => true,
            'inEdit' => true,
            'fieldAttributes' => [
                'rules' => '',
                'type' => 'input',
                'options' => '{"1" : "Yes", "0": "No"}',
            ],
        ];
        $this->resetValidation('fields');
    }
    public function getAdvancedSettingLabel($key)
    {
        //Str::replace does not exist in pre v8.41.0
        return Str::title(str_replace(['-','_'], [' ',' '], Str::kebab($key)));
    }

My congratulations on the excellent application! Great job!

I leave here my report regarding the "difficulties" I faced with the last release:

After generating a CRUD with the application I encountered the following situation:

• In the main view with the generated directive as below:
  @livewire('LaravelTips')

• And in the child view with the generated directive as below:
  @livewire('LaravelTips-child') @livewire('livewire-toast')

• However, when accessing the CRUD, an exception was thrown:

Livewire\Exceptions\ComponentNotFoundException
Unable to find component: [LaravelTips] and;
Livewire\Exceptions\ComponentNotFoundException
Unable to find component: [LaravelTips-child] respectively.

• In my case, it worked by being corrected to:
  @livewire('LaravelTips') and child to
  @livewire('laravel-tips-child') @livewire('livewire-toast')

Another thing I noticed was that, apparently, the LIVEWIRE components, are being generated during the CRUD steps and, at the end when being named the component does not finish the CRUD generation under the claim that the name is already in use!

Thx.