-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make allowed_classes configurable when unserializing formState #144
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 by reading. Thanks you, @ger4003 !
I'm just not sure about the target branch. IIRC features can only go into a |
I can change the target branch to |
yes please. Thanks |
@ger4003 Just a little update: I'm currently reviewing this and the change works great, but we are currently discussing whether the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And here is the update:
I think this one is obsolete with #145 and can be closed.
Thanks again and sorry for the inconvenience!
#close in favor of #145 |
With a new configuration option it is possible to add class names to
allowed_classes
forunserialize()
formState withinFormRuntime::initializeFormStateFromRequest
closes #143