Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

xabbuh
Copy link
Member

@xabbuh xabbuh commented Nov 13, 2018

Q A
Branch? 3.4
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets ##29187
License MIT
Doc PR

alternative to #29188

@@ -270,7 +270,7 @@
{# Errors #}

{% block form_errors -%}
{%- if errors|length > 0 -%}
{%- if render_errors|default(false) and errors|length > 0 -%}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

im not sure i get it.. this makes form_errors practically a no-op by default right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, and that's also why I am not convinced that we should make the change in core. It might break custom form themes. I rather tend to fix the documentation instead.

Copy link
Contributor

@ro0NL ro0NL Nov 14, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it could work like form_rest is working maybe; only render errors in form_errors if not already rendered

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

either way, 👍 for better docs: customizing form errors inside the label vs. outside the label.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or maybe make the current feature more explicit: form_label_with_errors? so if you start customizing based on core files you'll understand you need to pick form_label+form_errors vs. form_label_with_errors

@nicolas-grekas
Copy link
Member

What's the status here?

@xabbuh
Copy link
Member Author

xabbuh commented Dec 12, 2018

@stof, @HeahDude and me discussed this at SymfonyCon. This is not the way to go. We need to make this more clear in the documentation.

@xabbuh xabbuh closed this Dec 12, 2018
@xabbuh xabbuh deleted the issue-29187 branch December 14, 2018 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants