raffcioo

Hi @jrushlow, thank you for response. It is corrent that `make:entity` do setters correctly according to what we select, nullable or not. But the question is is it correct in...

I just made the testing :) created myself what I wrote above, trying to reproduce, in clean environment, and surprise... I got HTTP422. Wow... thats imposible I thought :) So......

So updated how to reproduce list looks like this: 1. create Symfony project 1. using make:entity make simple entity with one field string, not nullable 1. make migration, migrate, add...

It is thrown in: `$form->handleRequest($request);` Using symfony console make:entity I have created Test entity which has only one field *name* (not nullable string) and in database I have one record...

This is happening only on edit/update so to notice it we have to send existing (**not new**) Entity object in form to the user with correct not null data (field...

For me this is clearly a kind of bug because if someone new came to Symfony and do everything correctly and according to official documentation he shouldn't but eventually will...

This is what I am doing exacly. I can't describe it better: 1. symfony new test_project --version="7.0.*" --webapp 2. open this project in editor and run: symfony serve 3. symfony...

I also have this problem. I have working app written in Symfony 6.4 using AssetMapper which came with Stimulus and Turbo itegrated and I also use Bootstrap. I wanted to...

@pa- I tried this but in my case it was not a solution because when I made all stimulus controllers lazy some GUI elements on frontend started flickering on first...