Button method for post / delete

[akulmehta]

Previous versions had a way to use the method('post') on an action button in order to get a post request https://github.com/Power-Components/powergrid-doc/blob/5x/docs/table-features/button-class.md#method.

However, I could not find any documentation of this in version 6.x.

When I try to use the method('post') like:

            return [
                Button::add('Restore')
                    ->slot('Restore')
                    ->class('pg-btn-white ...')
                    ->route('items.restore', ['item' => $row->uuid])
                    ->method('post'),
            ];

I get the error: " Method PowerComponents\LivewirePowerGrid\Button::method does not exist. "

There is a line for the method in the src/Button.php file like:

// line 18
 * @method static method(string $method)

How do you create an action button to post or delete routes?

[luanfreitasdev]

This is no longer available in v6 for maintainability purposes. But you can create a custom one using customContent (needs docs 😄)

Column::make('custom-action')
  ->customContent([
      'view' => 'components.custom-action',
      'params' => []
 ])

[akulmehta]

@luanfreitasdev thanks. Could you provide a more clear example - maybe one with my use case above with the restore button?

[akulmehta]

Ok. I am trying this

            Column::make('Restore')
                ->customContent([
                    'view' => 'components.custom-action-button',
                    'params' => [
                        'route' => route('boxes.restore', ['box' => $row->id]),
                        'methodAttribute' => 'post',
                        'label' => 'Restore',
                    ],
                ]),

But since $row->id is not there how can I get the $row->id in the columns?

[luanfreitasdev]

The $row is sent because of the include, there is no need to pass it in the parameter, use it in the view

[backstageel]

@luanfreitasdev would you mind to explain what maintainability overhead this feature was bringing? Because it seems that it was a really good approach and I desperately need to use something like the method() approach.

Creating a new view/action for this seems too much