Chapters

41 Chapters | 4:45:40 |

01

Form Type Class

9:11
02

Handling the Form Submit

8:44
03

Success (Flash) Messages

6:50
04

Bind Your Form to a Class

7:32
05

Field Types & Options

4:45
06

DateTimeType & Data "Transforming"

6:25
07

EntityType: Drop-downs from the Database

7:33
08

EntityType: Custom Query

5:27
09

HTML5 & "Sanity" Validation

6:19
10

Validation Constraints with @Assert

5:13
11

Form Rendering Functions: form_*

5:22
12

Form Rendering Variables

5:16
13

The Edit Form

7:18
14

Registration Form

7:15
15

Adding Extra "Unmapped" Fields

6:58
16

UniqueEntity & Validation Directly on Form Fields

6:40
17

Agree to Terms Database Field

6:03
18

Agree to Terms Checkbox Field

5:35
19

All about Form Themes

8:01
20

Form Theme Block Naming & Creating our Theme!

6:22
21

Form Theming & Variables

8:42
22

Form Theming a Single Field

4:07
23

Custom Field Type

6:24
24

Data Transformer

9:09
25

Custom Field: configureOptions() & Allowing Empty Input

4:42
26

Leveraging Custom Field Options

5:35
27

Autocomplete JavaScript

8:19
28

Autocomplete Endpoint & Serialization Group

5:26
29

Hooking up the AJAX Autocomplete

8:20
30

The buildView() Method

7:09
31

Form Type Extension

10:09
32

Tweak your Form based on the Underlying Data

8:35
33

Form Model Classes (DTOs)

9:59
34

Custom Validator

8:59
35

Setup: For Dependent Select Fields

6:41
36

Form Events & Dynamic ChoiceType choices

6:01
37

Dynamic Form Events

7:40
38

PRE_SET_DATA: Data-based Dynamic Fields

4:25
39

JS to Auto-Update the Select Options

10:18
40

Clear that Location Name Data

5:09
41

A bit of Security Cleanup

7:02

This tutorial has a new version, check it out!

> Symfony 4 > Symfony 4 Forms: Build, Render & Conquer!

Buy Access to Course

10.

Validation Constraints with @Assert

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $12.00

Previous Chapter

Next Chapter

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Login or register to check out the script

33 Comments

Sort By

Login or Register to join the conversation

Omar-Drb hace 3 años

Hey I am using Symfony 6 with Php 8,

When I use the NotBlanck assert for example:

#[ORM\Column(length: 180, unique: true)]
#[Assert\NotBlank(message: "validator.message.notNullableField")]
private ?string $username = null;

public function getUsername(): ?string
{
    return $this->username;
}

public function setUsername(string $username): self
{
    $this->username = $username;

    return $this;
}

and add the "novalidate" on the form and submit, I get "HTTP 500 Error" with the following message:

Expected argument of type "string", "null" given at property path "username".

The problem is that the assert is never reached, there are 2 possible solutions:

Add a "?" to the setter parameter:

public function setUsername(?string $username): self
{
 $this->username = $username;

 return $this;
}

Add "empty_data" value to the form builder:

$builder
 ->add('username', null, [
     'empty_data' => ''
 ]);

But I don't find it very convenient to use these solutions on almost every filed on every entity!

My question is what is the best practice for this situation? Knowing that in the normal flow for normal users, they will get the HTML5 error "please fill out this field". Only the bad users will try to do this and will get the 500 Error.

|

MolloKhan SFCASTS Omar-Drb hace 3 años

Hey Omar,

In this case, you need to add another constraint, the "NotNull" constraint https://symfony.com/doc/current/reference/constraints/NotNull.html

Cheers!

1 |

Farshad hace 5 años

@Assert\NotBlack(message="Please fill in ..")
Messsage is not working. It keeps saying 'Example invalid select feedback' underneath input fields. Also the little red Error label is not showing.

|

Victor SFCASTS Farshad hace 5 años

Hey Farry7,

Haha, it makes sense, as it says "NotBlack" but your would need "NotBlank" ;) I'd recommend you to use PhpStorm with enabled Symfony plugin for autocompletion class names, it may help avoiding such problems. Btw, don't forget about using the correct namespace for that constraint as well!

Cheers!

1 |

Farshad hace 5 años

use Symfony\Component\Validator\Context\ExecutionContextInterface;
undefined namescpace "Contenxt" when I mouseover it on PHPStorm.
It doesnt work.

|

weaverryan SFCASTS Farshad hace 5 años

Hey @Farry7!

Hmm, that's interesting. That IS the correct namespace & interface name - you can see in, for example, Symfony 5.2 right here: https://github.com/symfony/...

Do you see a vendor/symfony/validator directory in your project? If it's not, make sure you install it - like we do here https://symfonycasts.com/sc...

Cheers!

|

Med Drh hace 6 años

Hello, How to add two atPath () ?, I tried to put -> atPath ('firstName')->atPath('lastName').is working just for one field :/

|

Victor SFCASTS Med Drh hace 6 años edited

Hey Med,

I'm afraid you cannot do this. The 2nd call of atPath() will override the previous value. What are you trying to achieve? Display the same message for a few fields? Try to build another second violation for this, like:


            $errorMessage = '%Your error message here%';
            $context->buildViolation($errorMessage)
                ->atPath('firstName')
                ->addViolation();
            $context->buildViolation($errorMessage)
                ->atPath('lastName')
                ->addViolation();

Just put your error message on a variable and use it to avoid duplications if needed.

I hope this helps!

Cheers!

1 |

Med Drh Victor hace 6 años

Thank you for your answer, I want to display the same error message for two different fields.
If I put a second violation I would have two identical messages for the two fields and I want only one error message: /
Message error : FirstName or lastName can't be null

|

Victor SFCASTS Med Drh hace 6 años

Hey Med,

Try to set the error message for the 2nd field only, the it should look good I think. Otherwise, you can think of splitting this error message into 2 separate about first name and last name. As an alternative, you can skip atPath() call and apply this error to the whole form instead of the specific field. This is more relevant for what you're trying to do - a general error for the whole form. If none of this fits you - go to the template and render your form yourself with form_error(), form_label(), form_widget() Twig functions. This will give you flexibility and you will render the error wherever you want.

I hope this helps!

Cheers!

1 |

paul-pleavin hace 6 años

So following this I can't seem to switch off the html5 validation to get the custom message fo blanl - I just get the browser instructing value cannot be empty

|

paul-pleavin paul-pleavin hace 6 años

Ah you needed to add 'required' => false - perfect!

3 |

Lijana Z. hace 6 años

"you do not apply the validation rules to the form" - you can apply to the form as I understand https://symfony.com/doc/4.4...

|

Victor SFCASTS Lijana Z. hace 6 años

Hey Coder,

Yes, you can apply validation rules to entities or to form types. General rules better apply to entities because those rules will work for all forms. But if you want to apply a specific rule for a specific form - you can do it too in the form type.

Cheers!

1 |

leonard Victor hace 6 años

Hello,
Will entity validation rules be overwritten by form validation rules?

|

Victor SFCASTS leonard hace 6 años

Hey Vali,

Good question! Actually, IIRC they should not override each other, they should "summarize". Like Validator will check both validation constraint you declared in your entity and in form type. You can easily double-check this ;)

Cheers!

|

Stephan hace 6 años

Hi,
I put @Assert\NotBlank() on the private $title property of the Article class but when I refresh I haven't the error message like you: "Error the value should not be blank". Can you explain me how I can solve that?

|

Akavir S. Stephan hace 6 años

Hey, don't forget to get the "required" field blank (with the inspector) or make your <input> novalidate into html :p

|

sadikoff Stephan hace 6 años

Hey @stephansav,

Are you just refreshing page? or re-submitting form? You should submit form again, because assertion works only when form is submitted

Cheers!

|

Marine GREGOIRE hace 6 años

Hi everyone !

I did @Assert on all my entities and that my form works. But what if I wanna use Ajax to display the data in a modal before submitting them ? How can I make the error messages appear then ? (Because I did it but since Ajax calls, reload is not happening and thus no error message are displayed. Any hint ?
I am lost :'(

Thanx

|

MolloKhan SFCASTS Marine GREGOIRE hace 6 años edited

Hey Marine GREGOIRE

You will need to implement an endpoint where you can submit the form's data, validate the fields and finally return the form's HTML. It would be almost the same logic as you already do but instead of doing "some" logic, such endpoint will always return the rendered form. Does it make any sense to you?

Cheers!

|

Jose M. hace 6 años

Hi everyone!

I´m just getting started with symfony and I'm trying out this Assert validation stuff...

I'm trying to make a field not empty and unique name with the following code:

class Portals
{
/**
* @ORM\Id()
* @ORM\GeneratedValue()
* @ORM\Column(type="integer")
*/
private $id;

/**
* @ORM\Column(name="name", type="string", length=255)
* @Assert\NotBlank(message="El portal debe tener un nombre.")
* @Assert\Unique(message="Este nombre ya existe")
*
*/

private $name;

And when I submit the form I get an "This value should be of type array|IteratorAggregate" no matter what I type in the field, it doesn't matter if the name already exists on the database or not, it just never goes through! is this a bug on 4.3??? Am I missing something???

Thanks for your help in advance!
-Orallo

|

MolloKhan SFCASTS Jose M. hace 6 años edited

Hey Jose M.

You are using the wrong constraint for your goal. Give it a look on the docs: https://symfony.com/doc/current/reference/constraints/Unique.html
that Unique constraint is for collections, the one you are looking for is UniqueEntity and it applies over the class. I'll leave you the docs here: https://symfony.com/doc/current/reference/constraints/UniqueEntity.html but if you have more doubts, let us know :)

Cheers!

|

Avraham M. hace 6 años

Hello!
Also regarding Automatic validation as described in link bellow

https://symfony.com/blog/ne...

Can you please explain how to make it work.

I have symfony 4.3 application, currently create Entities,

really do not want to add Validator annotations manually.

Lets say I have a field notNull

/**

* @var string

* @ORM\Column(name="title", type="string", length=10, nullable=false)

*/
private $title;

and in controller
leaving title property empty and validating

$errors = $validator->validate($post);
finds no errors.

Thanks!

Avraham

|

Victor SFCASTS Avraham M. hace 6 años edited

Hey Avraham,

First of all, you need to upgrade your Symfony application to the latest 4.3 version, the version we use in this screencasts does not support it yet. Then, follow the instructions in that blog post you linked. And finally, you would need to enable this feature in your config/packages/validator.yaml like:


framework:
    validation:
        email_validation_mode: html5

        # Enables validator auto-mapping support.
        # For instance, basic validation constraints will be inferred from Doctrine's metadata.
        auto_mapping:
            App\Entity\: []

And then it should work I think. But it has an issue IIRC, you can follow this thread to get more information why it's not enabled by default:
https://github.com/symfony/recipes/pull/612

I hope this helps!

Cheers!

|

Avraham M. Victor hace 6 años

Hey Victor!
Uncommenting

auto_mapping:
App\Entity\: []

from validator.yaml enabled Automatic validation!!!

Github discussion say this caused issue with forms
https://github.com/symfony/...

Yet Automatic Validation works.

Thank you very much!

|

Victor SFCASTS Avraham M. hace 6 años

Hey Avraham,

Great, glad it works for you. This is an awesome new feature indeed.

Cheers!

|

Krzysztof K. hace 6 años edited

Hello Guys I need your help, recently we have updated to Symfony 4.3 where new feature was introduced for auto validation.
I now I have new issues... or I need some extra explanation or there is a bug...
In my entity I have such definition for a property:

`
/**

@ORM\Column(type="string", length=128)
@Assert\NotBlank()
*/
private $tag;

public function getTag(): ?string
{
return $this->tag;
}

public function setTag(string $tag): self
{
$this->tag = $tag;
return $this;
}
`

With such setup like above when I edit entity and submit empty value I got following error: "This value should be of type string." previously I had (Symfony 4.2): "This value should not be blank."

But when I create new entity I get correct error message, somehow behaviour for create and edit is different in Symfony 4.3?

Why my validators do not have priority, why these automatic ones are executed first?

Also I have noticed that if I will remove type (string) form setter then this works and I get correct message. Should I then remove these from all my entities?

How can I overwrite this message automatic message: This value should be of type string.

How I can disable this functionality in my project?

|

Victor SFCASTS Krzysztof K. hace 6 años edited

Hey Krzysztof

For translating validation messages you can follow this guide: https://symfony.com/doc/current/validation/translations.html
And for disabling the auto validation system. Hmm, If I recall correctly it should be disabled by default but I believe you can disable it by changing the "framework.validation" configuration


// config/packages/validation.yaml
framework:
validation:
auto_mapping: []

Give it a try and let us know if it worked.

Cheers!
Diego

|

Krzysztof K. Victor hace 6 años

Thanks Victor, but what about validation priority? Can my validator be executed first? I was unable to find any additional info about this new feature.

|

Victor SFCASTS Krzysztof K. hace 6 años

Hey Krzysztof,

What do you mean? What your validator exactly? Fairly speaking, I'm not sure there's any priorities in applying validation constraints, maybe try to change their order? They might be applied in order how they are declared.

I hope this helps!

Cheers!

|

Krzysztof K. Krzysztof K. hace 6 años

Guys, any news on above?

|

Victor SFCASTS Krzysztof K. hace 6 años

Hey Krzysztof,

Oh, thanks for this ping! Our teammate Diego replied to you the next day, but somehow that message get lost, I restored it from the history, see the answer here: https://symfonycasts.com/sc...

We're sorry about it!

Cheers!

|

Symfony 4

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.1.3",
        "ext-iconv": "*",
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "doctrine/annotations": "^1.0", // 1.10.2
        "doctrine/doctrine-bundle": "^1.6.10", // 1.10.2
        "doctrine/doctrine-migrations-bundle": "^1.3|^2.0", // v2.0.0
        "doctrine/orm": "^2.5.11", // v2.7.2
        "knplabs/knp-markdown-bundle": "^1.7", // 1.7.0
        "knplabs/knp-paginator-bundle": "^2.7", // v2.8.0
        "knplabs/knp-time-bundle": "^1.8", // 1.8.0
        "nexylan/slack-bundle": "^2.0,<2.2.0", // v2.0.0
        "php-http/guzzle6-adapter": "^1.1", // v1.1.1
        "phpdocumentor/reflection-docblock": "^3.0|^4.0", // 4.3.0
        "sensio/framework-extra-bundle": "^5.1", // v5.2.1
        "stof/doctrine-extensions-bundle": "^1.3", // v1.3.0
        "symfony/asset": "^4.0", // v4.1.6
        "symfony/cache": "^3.3|^4.0", // v4.1.6
        "symfony/console": "^4.0", // v4.1.6
        "symfony/flex": "^1.0", // v1.21.6
        "symfony/form": "^4.0", // v4.1.6
        "symfony/framework-bundle": "^4.0", // v4.1.6
        "symfony/property-access": "^3.3|^4.0", // v4.1.6
        "symfony/property-info": "^3.3|^4.0", // v4.1.6
        "symfony/security-bundle": "^4.0", // v4.1.6
        "symfony/serializer": "^3.3|^4.0", // v4.1.6
        "symfony/twig-bundle": "^4.0", // v4.1.6
        "symfony/validator": "^4.0", // v4.1.6
        "symfony/web-server-bundle": "^4.0", // v4.1.6
        "symfony/yaml": "^4.0", // v4.1.6
        "twig/extensions": "^1.5" // v1.5.2
    },
    "require-dev": {
        "doctrine/doctrine-fixtures-bundle": "^3.0", // 3.0.2
        "easycorp/easy-log-handler": "^1.0.2", // v1.0.7
        "fzaninotto/faker": "^1.7", // v1.8.0
        "symfony/debug-bundle": "^3.3|^4.0", // v4.1.6
        "symfony/dotenv": "^4.0", // v4.1.6
        "symfony/maker-bundle": "^1.0", // v1.8.0
        "symfony/monolog-bundle": "^3.0", // v3.3.0
        "symfony/phpunit-bridge": "^3.3|^4.0", // v4.1.6
        "symfony/stopwatch": "^3.3|^4.0", // v4.1.6
        "symfony/var-dumper": "^3.3|^4.0", // v4.1.6
        "symfony/web-profiler-bundle": "^3.3|^4.0" // v4.1.6
    }
}

Previous Chapter

Next Chapter