7. Deleting resource¶

Deleting a resource is simple.

# routing.yml

app_user_delete:
    path: /users/{id}
    methods: [DELETE]
    defaults:
        _controller: app.controller.user:deleteAction

7.1. Calling the action with method DELETE¶

Currently browsers do not support the “DELETE” http method. Fortunately, Symfony has a very useful feature. You can make a POST call with override parameter, which will force the framework to treat the request as specified method.

<form method="post" action="{{ path('app_user_delete', {'id': user.id}) }}">
    <input type="hidden" name="_method" value="DELETE" />
    <button type="submit">
        Delete
    </button>
</form>

On submit, the delete action with the method DELETE, will remove and flush the resource. Then, by default it redirects to app_user_index to display the users index, but like for other actions - it’s customizable.

7.2. Overriding the criteria¶

By default, the deleteAction will look for the resource by id. However, you can easily change that. For example, you want to delete the user who belongs to particular company, not only by his id.

# routing.yml

app_user_delete:
    path: /companies/{companyId}/users/{id}
    methods: [DELETE]
    defaults:
        _controller: app.controller.user:deleteAction
        _sylius:
            criteria:
                id:      $id
                company: $companyId

There are no magic hacks behind that, it simply takes parameters from request and builds the criteria array for the findOneBy repository method.

7.3. Custom redirect after success¶

By default the controller will try to get the id of the resource and redirect to the “index” route. To change that, use the following configuration.

# routing.yml

app_user_delete:
    path: /competition/{competitionId}/users/{id}
    methods: [DELETE]
    defaults:
        _controller: app.controller.user:deleteAction
        _sylius:
            redirect:
                route: app_competition_show
                parameters: { id: $competitionId }