Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Add a data_help method in Form#26332

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
fabpot merged 35 commits intosymfony:masterfrommpiot:form_help
Mar 27, 2018
Merged

Add a data_help method in Form#26332

fabpot merged 35 commits intosymfony:masterfrommpiot:form_help
Mar 27, 2018

Conversation

@mpiot
Copy link
Contributor

@mpiotmpiot commentedFeb 27, 2018
edited
Loading

QA
Branch?master
Bug fix?no
New feature?yes
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed tickets#26331
LicenseMIT
Doc PRsymfony/symfony-docs#9361

Add a form_help method in twig to display a help message in form. Ahelp keyword is added to all FormType to define the message.

sstok, mricherzhagen, andreybolonin, and loru88 reacted with heart emoji
Copy link
Member

@stofstof left a comment

Choose a reason for hiding this comment

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

This is missing tests


{%blockform_help -%}
{%ifform.vars.helpis notempty %}
<smallclass="form-text text-muted">{{form.vars.help|raw }}</small>
Copy link
Member

Choose a reason for hiding this comment

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

displaying it raw is a bad idea IMO. It opens the door to XSS.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Mmm, is it really a problem ? Because it's set in the FormType by the dev, not by a user. Then, if we want use html in the help text without raw, we can't. I don't really know

Copy link
Member

@stofstofFeb 27, 2018
edited
Loading

Choose a reason for hiding this comment

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

Well, requiring to perform HTML escaping when setting the option is insecure IMO. It requires all devs to be aware that this options requires escaping when setting it. And it might totally be set based on some user input (coming from a previous configuration elsewhere) in some cases.

Btw, I would add translation support for the help text instead of requiring to translate it in the form type when setting the option.

Copy link
ContributorAuthor

@mpiotmpiotFeb 27, 2018
edited
Loading

Choose a reason for hiding this comment

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

Ok, I remove it from Symfony, if someone want to change it, just to extend the Template and add the raw.

By translation you mean use|trans in Twig ?

Copy link
Member

Choose a reason for hiding this comment

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

yes, as done for labels or other things

{# Help#}

{%blockform_help -%}
{%ifform.vars.helpis notempty %}
Copy link
Member

Choose a reason for hiding this comment

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

justhelp

Copy link
ContributorAuthor

@mpiotmpiotFeb 27, 2018
edited
Loading

Choose a reason for hiding this comment

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

Thx for the shortcut, I edit it

@mpiot
Copy link
ContributorAuthor

mpiot commentedFeb 27, 2018
edited
Loading

Yes, I fix existing tests, and wite new (I've never do it, it take a little times, sorry...)

Copy link
Member

@NyholmNyholm left a comment

Choose a reason for hiding this comment

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

Great. Thank you for contributing this.


{%blockform_help -%}
{%ifhelpis notempty %}
<smallclass="form-text text-muted">{{help|trans }}</small>
Copy link
Member

Choose a reason for hiding this comment

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

Let's make sure it respects the translation domain.

{{ translation_domain is same as(false) ? help : help|trans({}, translation_domain) }}

vudaltsov reacted with thumbs up emoji
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Okay, I edit it. (I don't really know what is it, but I trust you ;-))

Copy link
Member

Choose a reason for hiding this comment

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

It checks iftranslation_domain is false, it it is we just printhelp. If it is not false we use translation with that domain.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

I was thinking about TranslationDomain, I don't know what it is, I'd watch.

Copy link
Member

@NyholmNyholmFeb 27, 2018
edited
Loading

Choose a reason for hiding this comment

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

Have a look here:http://symfony.com/doc/current/components/translation.html#using-message-domains

It is basically a way to categorize translation messages.

Make sure you add this fix every time you printhelp. (ie in the form_div_layout.html.twig)

Copy link
ContributorAuthor

@mpiotmpiotFeb 27, 2018
edited
Loading

Choose a reason for hiding this comment

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

Thanks, and it's done :-) (it's interresting to do PR, it permit to learn lot of things:-))

@mpiot
Copy link
ContributorAuthor

Just a question, how can I execute tests ? Because when I do:

COMPOSER_ROOT_VERSION=4.0 composer installvendor/bin/simple-phpunit src/Symfony/Bridge/Twig/Tests

It return to me alle is ok, but Skip a lot of tests, but in TravisCi, it doesn't skip test and there is a lot of error, I can't try and push everytime to see what say Travis :-(

I've try to do something like travis do:

cd src/Symfony/Bridge/Twigcomposer update --no-progress --ansi --prefer-lowest --prefer-stableSYMFONY_ROOT_DIR/phpunit --exclude-group tty,benchmark,intl-data

But it does less tests, Skip all, and thrw an exception:

Other deprecation notices (1)
1x: The each() function is deprecated. This message will be suppressed on further calls

Thanks a lot, and sorry, it's the first tim I'm looking into tests... (I know, it's wrong... :p)

@Nyholm
Copy link
Member

I usually do./phpunit src/Symfony/Bridge/Twig. That should not skip the tests.

Here is a page that describes this in details:https://symfony.com/doc/current/contributing/code/tests.html

@Nyholm
Copy link
Member

Btw, I see that it is the "deps low" test that fails on Travis. That is okey for this PR since the changes on the different components depends on each other.

@mpiot
Copy link
ContributorAuthor

Oki, but I thought it would be nice to add tests for the new elements, right?

Test theform_help output, and then, maybe it change something form theform_row, no ?

@Nyholm
Copy link
Member

That would be excellent.

@javiereguiluz
Copy link
Member

I'm pinging some of our biggest Symfony Form experts so they can double check these changes:@HeahDude,@vudaltsov,@yceruto Thanks!

mpiot and ismail1432 reacted with thumbs up emojiNyholm reacted with heart emoji

@mpiot
Copy link
ContributorAuthor

Thank you :-)
Because I'm not very comfortable with Symfony Form, I'm just discovering the insides.

@nicolas-grekasnicolas-grekas added this to the4.1 milestoneFeb 27, 2018
Copy link
Contributor

@vudaltsovvudaltsov left a comment

Choose a reason for hiding this comment

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

Great PR, I like it.
Since we support Foundation framework, we should probably addform_help there too.

@Nyholm
Copy link
Member

Excellent. This looks real good.

(Bootstrap 4):
screen shot 2018-02-28 at 19 00 09


There is one thing I'm missing. You need to add anid to the help block (id="{{id}}_help) and use thearia-describedby on the<input>.

<labelfor="inputPassword5">Password</label><inputtype="password"id="inputPassword5"class="form-control"aria-describedby="passwordHelpBlock"><smallid="passwordHelpBlock"class="form-text text-muted">  Your password must be 8-20 characters long, contain letters and numbers, and must not contain spaces, special characters, or emoji.</small>
sstok reacted with hooray emojisstok reacted with heart emoji

@mpiot
Copy link
ContributorAuthor

mpiot commentedFeb 28, 2018
edited
Loading

@Nyholm I fix it tomorrow :-)

@Nyholm
Copy link
Member

Good. We also need the the aria-describedby on the .

After that I’m very happy.

@mpiot
Copy link
ContributorAuthor

@Nyholm This is done, just a little reflexion to avoid add the aria-describedBy, when there is not helpBlock. And some difficulties in the FrameworkBundle views, I don't know wwhat is its usage, but I don't like it :p

Copy link
Member

@NyholmNyholm left a comment

Choose a reason for hiding this comment

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

Good job. I did a much more thorough review now.

Could you also make sure fabbot is happy?


{%blockform_help -%}
{%ifhelpis notempty %}
<smallid="{{id }}HelpBlock"class="form-text text-muted">{{translation_domainissame as(false)?help:help|trans({},translation_domain) }}</small>
Copy link
Member

Choose a reason for hiding this comment

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

id generated by symfony is snake_case. I suggest changing this to{{ id }}_help

{{- form_label(form) -}}
{{- form_errors(form) -}}
{{- form_widget(form) -}}
{{- form_widget(form, {'helpBlockDisplayed':true }) -}}
Copy link
Member

Choose a reason for hiding this comment

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

Couldn't we check ifhelp is not empty here?
That would make the logic inwidget_attributes simpler

Copy link
ContributorAuthor

@mpiotmpiotMar 1, 2018
edited
Loading

Choose a reason for hiding this comment

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

The problem is when a user just displayform_widget for exemple, theform_help is not call, then we don't have to display the aria-describedBy, because the block doesn't exists.

That's why I do the test later, else, user say if he declare the form_help to do the link between help block and input.

In the row, I do it automatically, because I'm sure the help block is displayed.

Copy link
Member

Choose a reason for hiding this comment

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

I see. Could we try something like:

{{- form_widget(form, { 'helpBlockDisplayed': (help is not empty) }) -}} or that may be a syntax error.

Copy link
ContributorAuthor

@mpiotmpiotMar 1, 2018
edited
Loading

Choose a reason for hiding this comment

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

It's the same problem, we can't do it automatically, the help may be set, but don't displayed if the user do:

{{ form_label(form.name) }}{{ form_errors(form.name) }}{{ form_widget(form.name) }}

He doesn't callform_label, then help is not displayed, but set in the form.

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, But it that a problem?

If the user do:

{{ form_label(form.name) }}{{ form_errors(form.name) }}{{ form_widget(form.name) }}

Thenno form help will be rendered and noaria-describedBy will be used.


If the user do:

{{ form_label(form.name) }}{{ form_errors(form.name) }}{{ form_widget(form.name) }}{{ form_help(form.name) }}

Then form helpwill be rendered but noaria-describedBy will be used.


We should only make sure that the logic is clean and when the user do:

{{ form_row(form.name) }}

Then form helpwill be rendered ANDaria-describedBy will be used.

Copy link
ContributorAuthor

@mpiotmpiotMar 1, 2018
edited
Loading

Choose a reason for hiding this comment

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

Yes, we can do that, I've do it to permit the user to add thearia-describedBy when don't useform_row. Then, I'm not really sure it's the best way to do, the method must work for all.

id="{{id }}" name="{{full_name }}"
{%-ifdisabled %} disabled="disabled"{%endif -%}
{%-ifrequired %} required="required"{%endif -%}
{%-ifhelpBlockDisplayedisdefinedandhelpBlockDisplayedandhelpis notempty %} aria-describedby="{{id }}HelpBlock"{%endif -%}
Copy link
Member

Choose a reason for hiding this comment

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

Replaceand helpBlockDisplayed and withand helpBlockDisplayed same as(true) and

@@ -0,0 +1,3 @@
<?phpif (!empty($help)):?>
<p id="<?phpecho$view->escape($id)?>HelpBlock" class="help-text"><?phpecho$view->escape(false !==$translation_domain ?$view['translator']->trans($help,array(),$translation_domain) :$help)?></p>
Copy link
Member

Choose a reason for hiding this comment

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

_help instead ofHelpBlock

id="<?phpecho$view->escape($id)?>" name="<?phpecho$view->escape($full_name)?>"<?phpif ($disabled):?> disabled="disabled"<?phpendif?>
<?phpif ($required):?> required="required"<?phpendif?>
<?phpecho$attr ?''.$view['form']->block($form,'attributes') :''?>
<?phpif (isset($helpBlockDisplayed) &&$helpBlockDisplayed && !empty($help)):?> aria-describedby="<?phpecho$view->escape($id)?>HelpBlock"<?phpendif?>
Copy link
Member

Choose a reason for hiding this comment

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

&& $helpBlockDisplayed && => && true === $helpBlockDisplayed &&

'attr' =>array(),
'post_max_size_message' =>'The uploaded file was too large. Please try to upload a smaller file.',
'upload_max_size_message' =>$uploadMaxSizeMessage,// internal
'help' =>'',
Copy link
Member

Choose a reason for hiding this comment

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

Should the default be an empty string or null? Spontaneously I would saynull, but Im sure there is a reason you chose the empty string.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

I've not test with null... But In the line bellow, we must define the accepted type that is string. That's why I've put an empty string. But Maybe it works well with null, I can try it. Tests will scream if it's not good.

Copy link
ContributorAuthor

@mpiotmpiotMar 1, 2018
edited
Loading

Choose a reason for hiding this comment

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

I confirm, if default is null, it trhown error because it expect a string value.

Copy link
Member

Choose a reason for hiding this comment

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

Okey, Could we make it expect a string value and null? Or maybefalse would make more sense.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

I can try if I can give him an array of possibilities, but I don't know if it works, I don't know this part of the code.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

It's okay :-)

$resolver->setAllowedTypes('help', ['string', 'NULL']);

Copy link
Member

Choose a reason for hiding this comment

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

Great


$this->assertMatchesXpath($html,
'/span
[@id="nameHelpBlock"]
Copy link
Member

Choose a reason for hiding this comment

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

Update id


$this->assertMatchesXpath($html,
'/p
[@id="nameHelpBlock"]
Copy link
Member

Choose a reason for hiding this comment

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

Update id

@mpiot
Copy link
ContributorAuthor

@Nyholm I've fixed some of your suggestions :-) Mmm, "Could you also make sure fabbot is happy?", how I do that ? :p

@Nyholm
Copy link
Member

Thanks!

Fabbot is a script that make sure all PRs follow code standard and it also runs some test for "common things". It is real great.

See the PR status.
screen shot 2018-03-01 at 09 49 42 copy

You see that there are some things fabbot complains about. Just copy the command and fabbot will fix things for you.

screen shot 2018-03-01 at 09 51 2

@mpiot
Copy link
ContributorAuthor

mpiot commentedMar 1, 2018
edited
Loading

Oh yes, I've see that, but the correction, isn't the way used in all the other files... That's why I've not fix it and keep the way used in existing files.

@Nyholm
Copy link
Member

No, you can trust the fabbot. It does only correct/review the files you've edited in this PR.

sstok reacted with thumbs up emoji

@mpiot
Copy link
ContributorAuthor

For exemple it say to fix:

<?php echo $view['form']->label($form) ?><?php echo $view['form']->errors($form) ?><?php echo $view['form']->widget($form, array('helpBlockDisplayed' => true)) ?><?php echo $view['form']->help($form) ?>

By:

<?php echo $view['form']->label($form); ?><?php echo $view['form']->errors($form); ?><?php echo $view['form']->widget($form, array('helpBlockDisplayed' => true)); ?><?php echo $view['form']->help($form); ?>

I've not edited other lines, just add one. That's why I've keep the syntax without the; at end.

It's the same everywhere, it want to add; at end of each php block, but it's actually used nowhere in the foldersrc/Symfony/Bundle/FrameworkBundle/Ressources/views/Form. That's why I don't really know if I must do like fabpot.io say or do like all files are.

@Nyholm
Copy link
Member

I guess fabbot has updated its rules since those other lines were added. I think we should follow the recommendations by fabbot in this case.

Copy link
Member

@NyholmNyholm left a comment

Choose a reason for hiding this comment

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

Could you also run the following to fix the license in the file headers:

curl https://fabbot.io/patch/symfony/symfony/26332/80c66414450cbf0148d4fac6288c83a8b72172ae/license.diff | patch -p0

{%blockform_row -%}
<divclass="form-group{%if (notcompoundorforce_error|default(false))andnotvalid %} has-error{%endif %}">
{{- form_label(form) -}}
{{- form_widget(form) -}}
Copy link
Member

Choose a reason for hiding this comment

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

We should make sure aria-describedby is enabled here

{%-endif -%}
<{{element|default('div') }} class="form-group">
{{- form_label(form) -}}
{{- form_widget(form) -}}
Copy link
Member

Choose a reason for hiding this comment

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

We should make sure aria-describedby is enabled here

<divclass="row">
<divclass="large-12 columns{%if (notcompoundorforce_error|default(false))andnotvalid %} error{%endif %}">
{{ form_label(form) }}
{{ form_widget(form) }}
Copy link
Member

Choose a reason for hiding this comment

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

We should make sure aria-describedby is enabled here

@mpiot
Copy link
ContributorAuthor

It bugs.... The diff is empty, the diff file doesn't exists and I've already apply the patch to add the licence header.

@fabpot
Copy link
Member

Thank you@mpiot.

vudaltsov reacted with hooray emoji

@fabpotfabpot merged commit585ca28 intosymfony:masterMar 27, 2018
fabpot added a commit that referenced this pull requestMar 27, 2018
This PR was merged into the 4.1-dev branch.Discussion----------Add a data_help method in Form| Q             | A| ------------- | ---| Branch?       | master| Bug fix?      | no| New feature?  | yes| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#26331| License       | MIT| Doc PR        |symfony/symfony-docs#9361Add a form_help method in twig to display a help message in form. A `help` keyword is added to all FormType to define the message.Commits-------585ca28 Add return type hint859ee03 Revert: remove comment line from twig templatesd723756 Fix some mistakesc74e0dc Use spaceless balises in Twig templates8b937ff Try without try/catch32bf1f6 Test the renderHelp method in all Tests about help to skip them if necessary.437b77e Skip renderHelp test as skipped if not overrided84be70 Update composer files075fcfd [FrameworkBundle] Add widgetAtt to formTable/form_rowf1d13a8 Fix Fabpot.io69ded67 Added form_help on horizontal design and removed special variablefd53bc5 Enable aria-described in row for all Templates98065d3 fabpot.io fixedb95f8 Use array long syntaxaada72c Set help option on nul as defaultf948147 Rename help id (snake_case)77fa317 Fix Test30deaa9 PSR fixbf4d08c Add aria-describedBy on input1f3a15e Rename id058489d Add an id to the help6ea7a20 Remove vars option from form_helpba798df FrameworkBundle Tests4f2581d Use array long syntaxf15bc79 Fix coding standardsc934e49 Add test without help set8094804 Add Tests067c681 Template for table, Foundation and Bootstrap 3d3e3e49 Fix: check translation domain2c2c045 Adapt existant tests831693a Add trans filtere311838 Remove raw filter for help8b97c1b Use a shortcut to acces help var in Twig template1b89f9d Add a template fot div_layoutc8914f5 Add a data_help method in Form
@mpiotmpiot deleted the form_help branchMarch 29, 2018 19:50
@fabpotfabpot mentioned this pull requestMay 7, 2018
javiereguiluz added a commit to symfony/symfony-docs that referenced this pull requestMay 16, 2018
This PR was squashed before being merged into the 4.1 branch (closes#9361).Discussion----------Add help option to FormTypeAdd documentation about the new featuresymfony/symfony#26332Commits-------5bdf708 Add help option to FormType
@mhujer
Copy link
Contributor

Maybe this should be added toUPGRADE-4.1.md as well? Because when you have yourown Form Type Extension to handlehelp attribute, it starts to render twice in the form.

@nicolas-grekas
Copy link
Member

Would you like to open this PR?

mhujer added a commit to mhujer/symfony that referenced this pull requestMay 27, 2018
mhujer added a commit to mhujer/symfony that referenced this pull requestMay 27, 2018
nicolas-grekas added a commit that referenced this pull requestMay 29, 2018
This PR was merged into the 4.1 branch.Discussion----------[Form] mention "help" field option in UPGRADE file| Q             | A| ------------- | ---| Branch?       | 4.1 <!-- see below -->| Bug fix?      | no| New feature?  | no <!-- don't forget to update src/**/CHANGELOG.md files -->| BC breaks?    | no     <!-- seehttps://symfony.com/bc -->| Deprecations? | no <!-- don't forget to update UPGRADE-*.md and src/**/CHANGELOG.md files -->| Tests pass?   | yes    <!-- please add some, will be required by reviewers -->| Fixed tickets | #...   <!-- #-prefixed issue number(s), if any -->| License       | MITWhen you have your own Form Extension to handle help option (e.g. similar to the one mentioned in the [blog post](https://symfony.com/blog/new-in-symfony-4-1-form-field-help)), it starts to render twice in the form after upgrading to 4.1 (where#26332 was added)<!--Write a short README entry for your feature/bugfix here (replace this comment block.)This will help people understand your PR and can be used as a start of the Doc PR.Additionally: - Bug fixes must be submitted against the lowest branch where they apply   (lowest branches are regularly merged to upper ones so they get the fixes too). - Features and deprecations must be submitted against the master branch.-->Commits-------744362a update UPGRADE-4.1 for feature#26332 Form field help option
nicolas-grekas added a commit that referenced this pull requestMay 31, 2018
* 4.1: (22 commits)  [HttpKernel] Fix restoring trusted proxies in tests  Update UPGRADE-4.0.md  [Messenger] Fix suggested enqueue adapter package  bumped Symfony version to 4.1.1  updated VERSION for 4.1.0  updated CHANGELOG for 4.1.0  Insert correct parameter_bag service in AbstractController  Revert "feature#26702 Mark ExceptionInterfaces throwable (ostrolucky)"  CODEOWNERS: some more rules  removed unneeded comments in tests  removed unneeded comments in tests  Change PHPDoc in ResponseHeaderBag::getCookies() to help IDEs  [HttpKernel] fix registering IDE links  update UPGRADE-4.1 for feature#26332 Form field help option  [HttpKernel] Set first trusted proxy as REMOTE_ADDR in InlineFragmentRenderer.  [Process] Consider \"executable\" suffixes first on Windows  Triggering RememberMe's loginFail() when token cannot be created  bumped Symfony version to 4.1.0  updated VERSION for 4.1.0-BETA3  updated CHANGELOG for 4.1.0-BETA3  ...
@loru88
Copy link
Contributor

Do you think it's possible to have this feature available also in Symfony 3.4?
I can't understand why this simple feature is stick just to Symfony 4

@xabbuh
Copy link
Member

@loru88 We never add new features in patch versions, but only do that in minor releases. You can read more about our release process athttp://symfony.com/doc/current/contributing/community/releases.html.

loru88 reacted with thumbs up emoji

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@nicolas-grekasnicolas-grekasnicolas-grekas left review comments

@stofstofstof left review comments

@xabbuhxabbuhxabbuh left review comments

@fabpotfabpotfabpot approved these changes

@NyholmNyholmNyholm approved these changes

+1 more reviewer

@vudaltsovvudaltsovvudaltsov approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

Feature❄️ Feature FreezeImportant Pull Requests to finish before the next Symfony "feature freeze"Status: Reviewed

Projects

None yet

Milestone

4.1

Development

Successfully merging this pull request may close these issues.

11 participants

@mpiot@Nyholm@javiereguiluz@fabpot@nicolas-grekas@mhujer@loru88@xabbuh@stof@vudaltsov@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp