Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Routing

This section is deprecated. However, as of now, the Sylius E-Commerce project is still resorting to this configuration so you might want to check it out.

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

Generating Generic CRUD Routing

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

Yaml
config/routes.yaml
app_book:
    resource: |
        alias: app.book
    type: sylius.resource
PHP
src/Entity/Book.php
use Sylius\Resource\Annotation\SyliusCrudRoutes;

#[SyliusCrudRoutes(
    alias: 'app.book',
)]

Results in the following routes:

php bin/console debug:router
------------------------ --------------- -------- ------ -------------------------
Name                     Method          Scheme   Host   Path
------------------------ --------------- -------- ------ -------------------------
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_show            GET             ANY      ANY    /books/{id}
app_book_bulk_delete     DELETE          ANY      ANY    /books/bulk-delete
app_book_delete          DELETE          ANY      ANY    /books/{id}

Using a Custom Path

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

Yaml
PHP

Results in the following routes:

Generating API CRUD Routing

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

Results in the following routes:

Excluding Routes

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

Yaml
PHP

Results in the following routes:

Generating Only Specific Routes

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

Yaml
PHP

Results in the following routes:

Generating Routing for a Section

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

Yaml

The generation results in the following routes:

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:

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

Using a Custom Form

If you want to use a custom form:

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

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:

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:

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.

Note

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

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:

Which will result in the following routes:

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:

Which will result in the following routes:

Go back to the documentation's index

PreviousServicesNextForms

Last updated

Was this helpful?