Field Types & Options

Hey Dmytro K.

Actually, that was my fault, I forgot to add the use statements to the scripts. So, sorry about that, but at least you can expand the code blocks and see the use statements

Cheers!

oh i didn't know i could do that. Thank you for pointing out!

Hey Viktor Z.

If you installed "StofDoctrineExtensionBundle", then you may have forgotten to activate the Timestampable extension

stof_doctrine_extensions:
    orm:
        default:
            timestampable: true

cheers!

Sure, that had already been done before.

Hmm, that's odd. If you have the extension activated and you are using the TimestampableEntity treat on your entity, it should just work. I think I'll need to see your code.
Also, just in case, try clearing the cache manually

rm -rf var/cache

I've found that issue: https://github.com/symfony/....
So, I've the same problem: I need the form (with data_class) to pass the validation but doesn't have "required by entity class" fields in form.
Is there a way to validate only posted form fields because required fields for entity which are not created by form will be created manually in controller.

Hey Viktor Z.

I think your best option is to create a new form with only *those* fields. Does it makes sense?

Cheers!

Unfortunately, I cannot completely understand you.
I’ll try to explain again what I mean :))
1) I’ve created a Form Class which is connected with an Entity Class via “data_class” parameter.
2) There are some required fields in connected Entity Class.
3) I don’t want a user fill all required entity fields in a form, so I call “add” method of “builder” only for those fields I want the user to fill.
4) When I call “is_valid” method inside controller, I can’t pass checks, because in controller I fetch an entity class object from a form but this object obviously doesn’t include entity class required fields.

So I want to call “set” methods for required fields manually in controller after I fetch object from form.

Hmm, I get what you are saying but I don't get why validations are not passing if the submitted form is indeed valid. From what you said I assume you are editing an User object. So, if you submit a valid form it should just work, unless you have, for some strange reason, invalid users on your Database. If that's not the case, then I'm missing something, probably would be useful if I can see your code. Just upload to anywhere (Github) and send me a link to it :)

Cheers!

Hi!
https://github.com/luntik43...
The problem is in src/Form/ContactFormType.php and src/Controller/PagesController.php@contacts

Hey Viktor Z.

I now understand your problem better. Here what you can do:
A) Create a DTO (Data transfer object) holding only the fields you want to submit, attach the class to your form and on submit, you will have to manually attach the other part of the data to your Support entity and then save it into the database. Or
B) Use the $clearMissing parameter. The only gotcha is that you will have to modify a bit how you handle POST requests but I'll leave you with the docs (they are easy to follow) and a video where Ryan uses it, but if you have more questions, feel free to ask us :)

Docs: https://symfony.com/doc/current/form/direct_submit.html
Video: https://symfonycasts.com/screencast/symfony-rest/patch-programmer

Cheers!

Is that a correct variant to use DTO and manually add data?
https://github.com/luntik43...

Unfortunately, your B variant didn't help.
I've updated the repository with the newest code.
Now I use PATCH method to submit the form, and set $clearMissing parameter to false.
https://github.com/luntik43...
The problem is still in src/Form/ContactFormType.php and src/Controller/PagesController.php@contacts

UPDATED: I've just used validation_groups and now there is no problem with 'topic' field, but there are still errors with time stamps. With validation_groups I don't need to use $clearMissing at all.
You can see the changes in commit history.

Thanks a lot!

Hey Viktor

I'm glad to know that you could fix your problem and of course, validation groups! They are great when the data model doesn't change but the constraints do depending on the action

Cheers!