5. Creating new resource¶

5.1. Declaring your form as a service¶

As said previously, you need to declare your form as a service. Its name must be contructed with the following pattern application_resource (Example: sylius_product). (see the Configuration chapter to see how configure your resources and your application name)

<parameters>
    <!-- If you use the basic configuration this paramter is not available in the container. You need to add it manually. -->
    <parameter key="app.form.type.user.class">App\Bundle\Form\UserType</parameter>
</parameters>

<services>
    <service id="app.form.type.user" class="%app.form.type.user.class%">
        <tag name="form.type" alias="app_user" />
    </service>
</services>

5.2. Submitting the form¶

You can use exactly the same route to handle the submit of the form and create the user.

<form method="post" action="{{ path('app_user_create') }}">

On submit, the create action with method POST, will bind the request on the form, and if it is valid it will use the right manager to persist the resource. Then, by default it redirects to app_user_show to display the created user, but you can easily change that behavior - you’ll see this in later sections.

When validation fails, it will render the form just like previously with the errors to display.

5.3. Changing the template¶

Just like for the show and index actions, you can customize the template per route.

# routing.yml

app_user_create:
    path: /users/new
    methods: [GET, POST]
    defaults:
        _controller: app.controller.user:createAction
        _sylius:
            template: App:Backend/User:create.html.twig

5.4. Using different form¶

You can also use custom form type on per route basis. By default it generates the form type name following the simple convention bundle prefix + _ + resource logical name. Below you can see the usage for specifying a custom form.

# routing.yml

app_user_create:
    path: /users/new
    methods: [GET, POST]
    defaults:
        _controller: app.controller.user:createAction
        _sylius:
            template: App:Backend/User:create.html.twig
            form: app_user_custom

or use use directly a class.

# routing.yml
app_user_create:
    path: /users/new
    methods: [GET, POST]
    defaults:
        _controller: app.controller.user:createAction
        _sylius:
            template: App:Backend/User:create.html.twig
            form: App\Byndle\Form\UserType

5.5. Using custom factory method¶

By default, ResourceController will use the createNew method with no arguments to create a new instance of your object. However, this behavior can be modified. To use different method of your repository, you can simply configure the factory option.

# routing.yml

app_user_create:
    path: /users/new
    methods: [GET, POST]
    defaults:
        _controller: app.controller.user:createAction
        _sylius:
            factory: createNewWithGroups

Additionally, if you want to provide your custom method with arguments from the request, you can do so by adding more parameters.

# routing.yml

app_user_create:
    path: /users/{groupId}/new
    methods: [GET, POST]
    defaults:
        _controller: app.controller.user:createAction
        _sylius:
            factory:
                method: createNewWithGroups
                arguments: [$groupId]

With this configuration, $repository->createNewWithGroups($request->get('groupId')) will be called to create new resource within createAction.

5.6. Custom redirect after success¶

By default the controller will try to get the id of the newly created resource and redirect to the “show” route. You can easily change that. For example, to redirect user to list after successfully creating a new resource - you can use the following configuration.

# routing.yml

app_user_create:
    path: /users/new
    methods: [GET, POST]
    defaults:
        _controller: app.controller.user:createAction
        _sylius:
            redirect: app_user_index

You can also perform more complex redirects, with parameters. For example...

# routing.yml

app_user_create:
    path: /competition/{competitionId}/users/new
    methods: [GET, POST]
    defaults:
        _controller: app.controller.user:createAction
        _sylius:
            redirect:
                route: app_competition_show
                parameters: { id: $competitionId }

In addition to the request parameters, you can access some of the newly created objects properties, using the resource. prefix.

# routing.yml

app_user_create:
    path: /users/new
    methods: [GET, POST]
    defaults:
        _controller: app.controller.user:createAction
        _sylius:
            redirect:
                route: app_user_show
                parameters: { email: resource.email }

With this configuration, the email parameter for route app_user_show will be obtained from your newly created user.