4. Routing

SyliusResourceBundle ships with a custom route loader that can save you some time.

4.1. Generating Generic CRUD Routing

To generate a full CRUD routing, simply configure it in your config/routes.yaml:

app_book:
    resource: |
        alias: app.book
    type: sylius.resource

Results in the following routes:

$ php bin/console debug:router

------------------------ --------------- -------- ------ -------------------------
Name                     Method          Scheme   Host   Path
------------------------ --------------- -------- ------ -------------------------
app_book_show            GET             ANY      ANY    /books/{id}
app_book_index           GET             ANY      ANY    /books/
app_book_create          GET|POST        ANY      ANY    /books/new
app_book_update          GET|PUT|PATCH   ANY      ANY    /books/{id}/edit
app_book_delete          DELETE          ANY      ANY    /books/{id}

4.2. Using a Custom Path

By default, Sylius will use a plural form of the resource name, but you can easily customize the path:

app_book:
    resource: |
        alias: app.book
        path: library
    type: sylius.resource

Results in the following routes:

$ php bin/console debug:router

------------------------ --------------- -------- ------ -------------------------
Name                     Method          Scheme   Host   Path
------------------------ --------------- -------- ------ -------------------------
app_book_show            GET             ANY      ANY    /library/{id}
app_book_index           GET             ANY      ANY    /library/
app_book_create          GET|POST        ANY      ANY    /library/new
app_book_update          GET|PUT|PATCH   ANY      ANY    /library/{id}/edit
app_book_delete          DELETE          ANY      ANY    /library/{id}

4.3. Generating API CRUD Routing

To generate a full API-friendly CRUD routing, add these YAML lines to your config/routes.yaml:

app_book:
    resource: |
        alias: app.book
    type: sylius.resource_api

Results in the following routes:

$ php bin/console debug:router

------------------------ --------------- -------- ------ -------------------------
Name                     Method          Scheme   Host   Path
------------------------ --------------- -------- ------ -------------------------
app_book_show            GET             ANY      ANY    /books/{id}
app_book_index           GET             ANY      ANY    /books/
app_book_create          POST            ANY      ANY    /books/
app_book_update          PUT|PATCH       ANY      ANY    /books/{id}
app_book_delete          DELETE          ANY      ANY    /books/{id}

4.4. Excluding Routes

If you want to skip some routes, simply use except configuration:

app_book:
    resource: |
        alias: app.book
        except: ['delete', 'update']
    type: sylius.resource

Results in the following routes:

$ php bin/console debug:router

------------------------ --------------- -------- ------ -------------------------
Name                     Method          Scheme   Host   Path
------------------------ --------------- -------- ------ -------------------------
app_book_show            GET             ANY      ANY    /books/{id}
app_book_index           GET             ANY      ANY    /books/
app_book_create          GET|POST        ANY      ANY    /books/new

4.5. Generating Only Specific Routes

If you want to generate only some specific routes, simply use the only configuration:

app_book:
    resource: |
        alias: app.book
        only: ['show', 'index']
    type: sylius.resource

Results in the following routes:

$ php bin/console debug:router

------------------------ --------------- -------- ------ -------------------------
Name                     Method          Scheme   Host   Path
------------------------ --------------- -------- ------ -------------------------
app_book_show            GET             ANY      ANY    /books/{id}
app_book_index           GET             ANY      ANY    /books/

4.6. Generating Routing for a Section

Sometimes you want to generate routing for different “sections” of an application:

app_admin_book:
    resource: |
        alias: app.book
        section: admin
    type: sylius.resource
    prefix: /admin

app_library_book:
    resource: |
        alias: app.book
        section: library
        only: ['show', 'index']
    type: sylius.resource
    prefix: /library

The generation results in the following routes:

$ php bin/console debug:router

------------------------ --------------- -------- ------ -------------------------
Name                     Method          Scheme   Host   Path
------------------------ --------------- -------- ------ -------------------------
app_admin_book_show      GET             ANY      ANY    /admin/books/{id}
app_admin_book_index     GET             ANY      ANY    /admin/books/
app_admin_book_create    GET|POST        ANY      ANY    /admin/books/new
app_admin_book_update    GET|PUT|PATCH   ANY      ANY    /admin/books/{id}/edit
app_admin_book_delete    DELETE          ANY      ANY    /admin/books/{id}
app_library_book_show    GET             ANY      ANY    /library/books/{id}
app_library_book_index   GET             ANY      ANY    /library/books/

4.7. Using Custom Templates

By default, ResourceController will use the templates namespace you have configured for the resource. You can easily change that per route, but it is also easy when you generate the routing:

app_admin_book:
    resource: |
        alias: app.book
        section: admin
        templates: Admin/Book
    type: sylius.resource
    prefix: /admin

Following templates will be used for actions:

  • :templates/Admin/Book:show.html.twig
  • :templates/Admin/Book:index.html.twig
  • :templates/Admin/Book:create.html.twig
  • :templates/Admin/Book:update.html.twig

4.8. Using a Custom Form

If you want to use a custom form:

app_book:
    resource: |
        alias: app.book
        form: App/Form/Type/AdminBookType
    type: sylius.resource

create and update actions will use App/Form/Type/AdminBookType form type.

Note

Remember, that if your form type has some dependencies you have to declare it as a service and tag with name: form.type. You can read more about it here

4.9. Using a Custom Redirect

By default, after successful resource creation or update, Sylius will redirect to the show route and fallback to index if it does not exist. If you want to change that behavior, use the following configuration:

app_book:
    resource: |
        alias: app.book
        redirect: update
    type: sylius.resource

4.10. API Versioning

One of the ResourceBundle dependencies is JMSSerializer, which provides a useful functionality of object versioning. It is possible to take an advantage of it almost out of the box. If you would like to return only the second version of your object serializations, use the following snippet:

app_book:
    resource: |
        alias: app.book
        serialization_version: 2
    type: sylius.resource_api

What is more, you can use a path variable to dynamically change your request. You can achieve this by setting a path prefix when importing file or specify it in the path option.

app_book:
    resource: |
        alias: app.book
        serialization_version: $version
    type: sylius.resource_api

Note

Remember that a dynamically resolved books prefix is no longer available when you specify path, and it has to be defined manually.

4.11. Using a Custom Criteria

Sometimes it is convenient to add some additional constraint when resolving resources. For example, one could want to present a list of all books from some library (which id would be a part of path). Assuming that the path prefix is /libraries/{libraryId}, if you would like to list all books from this library, you could use the following snippet:

app_book:
    resource: |
        alias: app.book
        criteria:
            library: $libraryId
    type: sylius.resource

Which will result in the following routes:

$ php bin/console debug:router

------------------------ --------------- -------- ------ ---------------------------------------
Name                     Method          Scheme   Host   Path
------------------------ --------------- -------- ------ ---------------------------------------
app_book_show            GET             ANY      ANY    /libraries/{libraryId}/books/{id}
app_book_index           GET             ANY      ANY    /libraries/{libraryId}/books/
app_book_create          GET|POST        ANY      ANY    /libraries/{libraryId}/books/new
app_book_update          GET|PUT|PATCH   ANY      ANY    /libraries/{libraryId}/books/{id}/edit
app_book_delete          DELETE          ANY      ANY    /libraries/{libraryId}/books/{id}

4.12. Using a Custom Identifier

As you could notice the generated routing resolves resources by the id field. But sometimes it is more convenient to use a custom identifier field instead, let’s say a code (or any other field of your choice which can uniquely identify your resource). If you want to look for books by isbn, use the following configuration:

app_book:
    resource: |
        identifier: isbn
        alias: app.book
        criteria:
            isbn: $isbn
    type: sylius.resource

Which will result in the following routes:

$ php bin/console debug:router

------------------------ --------------- -------- ------ -------------------------
Name                     Method          Scheme   Host   Path
------------------------ --------------- -------- ------ -------------------------
app_book_show            GET             ANY      ANY    /books/{isbn}
app_book_index           GET             ANY      ANY    /books/
app_book_create          GET|POST        ANY      ANY    /books/new
app_book_update          GET|PUT|PATCH   ANY      ANY    /books/{isbn}/edit
app_book_delete          DELETE          ANY      ANY    /books/{isbn}