You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using nested options with in depth normalisation in a form, the following profiler error occurs:
An exception has been thrown during the rendering of a template ("Notice: Object of class Symfony\Component\VarDumper\Cloner\Data could not be converted to int").
The traceback error occurs in vendor/symfony/web-profiler-bundle/Resources/views/Collector/form.html.twig:651, but I could not find an obvious reason for this error.
Greetings!
Seems extracting passed/resolved value works incorrect when null/false passed/resolved
So I sent PR where I have tried to fix the problem. Maybe codestyle should be fixed, because of ternary
…resolved options are defined (vltrof)
This PR was submitted for the 6.4 branch but it was merged into the 5.4 branch instead.
Discussion
----------
[WebProfilerBoundle] form data collector check passed and resolved options are defined
| Q | A
| ------------- | ---
| Branch? | 6.4
| Bug fix? | yes
| New feature? | no
| Deprecations? | no
| Issues | Fix#58665
| License | MIT
Greetings!
When passed or resolved value casted to false (null/false) it sets wrong value what cause exceptions described in issue. Explicit check if value defined prevent this behavior
Maybe codestyle should be fixed because of ternary
Commits
-------
93faa96 profiler form data collector extart value property if it is setted
Symfony version(s) affected
6.4.12
Description
When using nested options with in depth normalisation in a form, the following profiler error occurs:
The traceback error occurs in
vendor/symfony/web-profiler-bundle/Resources/views/Collector/form.html.twig:651
, but I could not find an obvious reason for this error.How to reproduce
Reproducer: https://github.com/7-zete-7/symfony-form-profiler-reproducer-1
Possible Solution
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: