When I use Select 2 and collapsed-card with Livewire it's not working properly?

[tmgomas]

| When I use Select 2 and collapsed-card with Livewire it's not working properly?

when I use the input field after select 2 is not working.

when I use collapsed card with Livewire I put some value on input field card is auto collapsed

Gender @foreach ($Genders as $key=>$Gender) {{ $Gender->gen_name }} @endforeach /select>

tmgomas commented 3 years ago

Expandable

            <div class="card-tools">
              <button type="button" class="btn btn-tool" data-card-widget="collapse"><i class="fas fa-plus"></i>
              </button>
            </div>
            <!-- /.card-tools -->
          </div>
          <!-- /.card-header -->
          <div class="card-body">
            The body of the card
          </div>
          <!-- /.card-body -->
        </div>

resslinger commented 3 years ago

@tmgomas is the issue actual?

setiawanjoko commented 3 years ago

@resslinger my Datatables doesn't work properly with livewire. Here is my project structure

+-- Main views
|   +-- Table livewire
|   |   + Action button livewire

I used Action Button Livewire to destroy a User (for example), and then calling a listener from parent livewire using emitUp(). The User already deleted but the table order is messed up. If I delete a user, then the search box and record number filter moved below the table. If I delete another user, then all elements disappeared except the table.

Should I use a package focused on Datatables in livewire or somebody have a solution?

dfsmania commented 3 years ago

@setiawanjoko I'm not familiarized with Livewire, but If you are deleting elements from the Datatable, I believe you have to do it using the API they provide. The documentation to remove is here: [remove()](https://datatables.net/reference/api/row().remove()). If you are only deleting the html code associated with a row, it will conflict with the information that Datatables is handling in memory.

• © Githubissues.
• Githubissues is a development platform for aggregating issues.

[tmgomas]

Expandable

            <div class="card-tools">
              <button type="button" class="btn btn-tool" data-card-widget="collapse"><i class="fas fa-plus"></i>
              </button>
            </div>
            <!-- /.card-tools -->
          </div>
          <!-- /.card-header -->
          <div class="card-body">
            The body of the card
          </div>
          <!-- /.card-body -->
        </div>

[resslinger]

@tmgomas is the issue actual?

[setiawanjoko]

@resslinger my Datatables doesn't work properly with livewire. Here is my project structure

+-- Main views
|   +-- Table livewire
|   |   + Action button livewire

I used Action Button Livewire to destroy a User (for example), and then calling a listener from parent livewire using emitUp(). The User already deleted but the table order is messed up. If I delete a user, then the search box and record number filter moved below the table. If I delete another user, then all elements disappeared except the table.

Should I use a package focused on Datatables in livewire or somebody have a solution?

[dfsmania]

@setiawanjoko I'm not familiarized with Livewire, but If you are deleting elements from the Datatable, I believe you have to do it using the API they provide. The documentation to remove is here: [remove()](https://datatables.net/reference/api/row().remove()). If you are only deleting the html code associated with a row, it will conflict with the information that Datatables is handling in memory.