-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[Console] Update input.rst #16810
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
[Console] Update input.rst #16810
Conversation
* 5.4: Remove reference to PHP Templates in translation
Hello, I think the condition `image_url is not null` is not enough as if we create a FileType form field without the `image_property` it causes an error. Adding `image_url is defined` is necessary because the variable `image_url` is only defined and passed to the view when `image_property` is already defined.
…amkhadiri1989) This PR was submitted for the 6.0 branch but it was merged into the 5.4 branch instead. Discussion ---------- [Form] Update create_form_type_extension.rst Hello, I think the condition `image_url is not null` is not enough as if we create a FileType form field without the `image_property` it causes an error. Adding `image_url is defined` is necessary because the variable `image_url` is only defined and passed to the view when `image_property` is already defined. <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/releases for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `6.x` for features of unreleased versions). --> Commits ------- 85470c5 Update create_form_type_extension.rst
UTF8 is meant to be used when using PostgreSQL, and the example is mainly about MySQL. In the case of MySQL, utf8 is a deprecated charset and should not be used.
…greg0ire) This PR was merged into the 5.4 branch. Discussion ---------- [Doctrine] Recommend a better charset for MySQL UTF8 is meant to be used when using PostgreSQL, and the example is mainly about MySQL. In the case of MySQL, utf8 is a deprecated charset and should not be used. <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/releases for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `6.x` for features of unreleased versions). --> Commits ------- 4f5845b Recommend a better charset for MySQL
This PR was merged into the 5.4 branch. Discussion ---------- [Uid] Update uid.rst Reference symfony/symfony#44938 (comment) <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/releases for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `6.x` for features of unreleased versions). --> Commits ------- 91872e4 Update uid.rst
* 5.4: Recommend a better charset for MySQL Update create_form_type_extension.rst Update uid.rst
* 4.4: remove reference to not existing YAML dumper flag
…ute (94noni) This PR was merged into the 5.4 branch. Discussion ---------- [Notifier] Update route from annotation to attribute I was reading some doc around this notifier component and found this is worth it Commits ------- eaa7f02 Update route from annotation to attribute
* 4.4: Use `path` instead of `url` in SSI documentation
Updates the FQCN for DoctrineReceiver as the class moved in a Bridge namespace after Symfony 6.0
…n 6.0 (AymDev) This PR was submitted for the 6.0 branch but it was merged into the 5.4 branch instead. Discussion ---------- [Messenger] Fix broken link to DoctrineReceiver in 6.0 Came across a broken link to the `DoctrineReceiver` class when building my Azure transport. Commits ------- 2036790 Fix broken link to DoctrineReceiver in Messenger
…smariegaborit) This PR was merged into the 5.4 branch. Discussion ---------- Encore : firewall replace with allowedHosts The firewall option was removed since webpack-dev-server V4.0.0 and replace with allowedHosts. https://github.com/webpack/webpack-dev-server/blob/master/CHANGELOG.md#bug-fixes-15 Commits ------- 9dc01ff firewall option replace with allowedHosts
This PR was merged into the 5.4 branch. Discussion ---------- Update _ux-libraries.rst.inc I was reading some doc on twig/live component and arrived on this page, As it seems they are not alpha ordered, for me the Swup integration could be defined upper as it is a more global lib than the chart or dropzone Commits ------- 96df416 Update _ux-libraries.rst.inc
… (Jibbarth) This PR was merged into the 5.4 branch. Discussion ---------- [Lock] Fix code example for Doctrine based stores Just noticed examples code for DoctrineDbalStore and DoctrineDbalPostgreSqlStore still used the old Pdo*Store. Commits ------- 9829b13 [Lock] Fix code example for Doctrine based stores
* 4.4: [Config] Suggest avoiding new environments
* 5.4: [Config] Suggest avoiding new environments Fix broken link to DoctrineReceiver in Messenger remove reference to not existing YAML dumper flag Update _ux-libraries.rst.inc firewall option replace with allowedHosts Update route from annotation to attribute Use `path` instead of `url` in SSI documentation [Lock] Fix code example for Doctrine based stores
This PR was merged into the 5.4 branch. Discussion ---------- Update README.markdown Ref [Symfony Releases Calendar](https://symfony.com/releases) Commits ------- 2d6fa20 Update README.markdown
…e (mdoutreluingne) This PR was merged into the 5.4 branch. Discussion ---------- [Mailer] Update route from annotation to attribute For this PR i update route from annotation to attribute Commits ------- e66b990 Update route from annotation to attribute
* 5.4: Update README.markdown Update route from annotation to attribute
Hello, According to the `getLongestCommonBasePath` signature, the method accepts a variadic string parameter $paths and not an array. It means when calling the `Path::getLongestCommonBasePath` with an array, a `TypeError` occurs. I think even the PHPDoc of the `Path::getLongestCommonBasePath` should be updated too as it is mentionned that it can accept an array argument.
…989) This PR was submitted for the 6.0 branch but it was merged into the 5.4 branch instead. Discussion ---------- [Filesystem] Update filesystem.rst Hello, According to the `getLongestCommonBasePath` signature, the method accepts a variadic string parameter $paths and not an array. It means when calling the `Path::getLongestCommonBasePath` with an array, a `TypeError` occurs. I think even the PHPDoc of the `Path::getLongestCommonBasePath` should be updated too as it is mentionned that it can accept an array argument. <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/releases for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `6.x` for features of unreleased versions). --> Commits ------- 2ebec3b Update filesystem.rst
* 5.4: Update filesystem.rst
* 4.4: Remove some unused links Remove usage of SymfonyCloud in favor of Platform.sh
Even if the default value is used
…om 6.0 docs (l-vo) This PR was merged into the 6.0 branch. Discussion ---------- [Security] Remove enable authenticator manager from 6.0 docs Related to symfony#16218 Commits ------- 1c76da8 Remove enable_authenticator_manager
* 4.4: Update doctrine.rst
* 5.4: Update doctrine.rst
* 4.4: Update the list of members of the CARE Team
* 5.4: Update the list of members of the CARE Team
…required even if the default value is used (l-vo) This PR was merged into the 5.4 branch. Discussion ---------- [Security] Creating a route for logout is always required even if the default value is used According to https://symfony.com/doc/current/security.html#logging-out and the fact that there is no default logout route defined in Symfony (at least I didn't find one). Commits ------- cb96633 Creating a route for logout is always required
* 5.4: Creating a route for logout is always required
…r needed) (mdoutreluingne) This PR was merged into the 6.0 branch. Discussion ---------- [Lock] Removed RetryTillSaveStore class (no longer needed) Fixes symfony#16785 For this PR, I removed `RetryTillSaveStore` class, because this class became obsolete from Symfony 5.2 and was removed from Symfony 6.0 as shown [here](https://github.com/symfony/symfony/pull/38296/files#diff-14c53c18273c57073d28f8dd3b4fab7253f5df427aea52b9a1c0a815dea3bea2). Commits ------- 0ba643e Remove RetryTillSaveStore class
* 4.4: [Form] Fix an inversion between object and class
* 5.4: [Form] Fix an inversion between object and class
…rator when possible (HeahDude) This PR was merged into the 5.4 branch. Discussion ---------- [DependencyInjection] Use PHP-DSL `env()` configurator when possible <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/releases for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `6.x` for features of unreleased versions). --> Fixes symfony#15223. Commits ------- e0e8a74 Use PHP-DSL `env()` configurator when possible
* 5.4: Use PHP-DSL `env()` configurator when possible
…norkunas) This PR was submitted for the 6.0 branch but it was merged into the 5.4 branch instead. Discussion ---------- [Security] Fix typehint in custom user provider Commits ------- 7fb76a5 [Security] Fix typehint in custom user provider
* 5.4: [Security] Fix typehint in custom user provider
VALUE_IS_ARRAY can't be used alone and must be combined with VALUE_REQUIRED or VALUE_OPTIONAL else we will get InvalidArgumentException('Impossible to have an option mode VALUE_IS_ARRAY if the option does not accept a value.')
@@ -221,7 +221,7 @@ There are five option variants you can use: | |||
Accept either the flag (e.g. ``--yell``) or its negation (e.g. | |||
``--no-yell``). | |||
|
|||
You can combine ``VALUE_IS_ARRAY`` with ``VALUE_REQUIRED`` or |
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.
So the following would be correct?
You need to combine
VALUE_IS_ARRAY
withVALUE_REQUIRED
or
VALUE_OPTIONAL
like this::
Being a bit picky, the original sentence is also correct, "you can combine VALUE_IS_ARRAY", but ofc you first need VALUE_REQUIRED
oder VALUE_OPTIONAL
(note that these two are written before the VALUE_IS_ARRAY
), but I am totally fine to make it more clear.
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.
What is confusing is that 'InputArgument::IS_ARRAY' and 'InputOption::VALUE_IS_ARRAY' can both be used combined and for both the same description is used 'You can combine...', so automatically i thought they both share the same logic, but only 'InputArgument::IS_ARRAY' can be used alone.
'You need to combine' it s more clear,
Thank you !
I think this should target |
I targeted 4.4 here: #16821 |
VALUE_IS_ARRAY can't be used alone and must be combined with VALUE_REQUIRED or VALUE_OPTIONAL else
we will get InvalidArgumentException('Impossible to have an option mode VALUE_IS_ARRAY if the option does not accept a value.')