311
657
33
🏗️ A skeleton to start a new web project with PHP, Docker and Invoke
Events
[VarDumper] Add a caster for the FlattenException
| Q | A | ------------- | --- | Branch? | 6.3 | Bug fix? | no | New feature? | yes | Deprecations? | no | Tickets | | License | MIT | Doc PR |
The information is duplicated, and when debuging messenger errors, the output is way too verbose. This PR enchance the situation.
[VarDumper] Add Caster::PATTERN_PRIVATE to help builing key
| Q | A | ------------- | --- | Branch? | 6.3 | Bug fix? | no | New feature? | yes | Deprecations? | no | Tickets | | License | MIT | Doc PR | not needed I guess
lyrixx push lyrixx/symfony
[Console] Add missing ZSH mention in DumpCompletionCommand help
lyrixx push lyrixx/symfony
[Console] Add missing ZSH mention in DumpCompletionCommand help
lyrixx push lyrixx/symfony
update documentation for telegram bridge notifier
minor #49811 [Notifier] Update documentation for telegram bridge notifier (MrYamous)
This PR was merged into the 6.2 branch.
Discussion
[Notifier] Update documentation for telegram bridge notifier
| Q | A | ------------- | --- | Branch? | 6.2 | Bug fix? | no | New feature? | no | Deprecations? | no | Tickets | From doc - Following #49782 | License | MIT | Doc PR |
Following #49782 to have up to date documentation in readme before removing it from symfony docs
Commits
1ddc90c21e update documentation for telegram bridge notifier
[Console] Add missing ZSH mention in DumpCompletionCommand help
Fix buildModel argument order when called via buildModelFromIndexAndData
Oh! That's strange. Can you add a test please?
symfony/workflow: custom marking store with access to property or arguments
If you use a custom service as a marking store, you are responsible of defining its arguments. I think it's a bad idea if Symfony allow to create new services from this part of the configuration.
However, I'll submit a PR to add a new kind of marking store to support property natively 👍🏼
lyrixx push lyrixx/lyrixx
Update README.md
[Console] Make sure signals registered by `SignalableCommandInterface` commands are defined in the PCNTL extension
| Q | A | ------------- | --- | Branch? | 6.3 | Bug fix? | no | New feature? | yes | Deprecations? | no | Tickets | NA | License | MIT | Doc PR | No need I guess
Makes me think that adding a similar method to check a signal existence as a string in SignalRegistry could be leveraged in https://github.com/symfony/symfony/pull/49750
[Console] Make sure signals registered by `SignalableCommandInterface` commands are defined in the PCNTL extension
Miss click, sorry! GitHub is really slow ATM 😬, I'll re-open as soon as GitHub allow me to!
[Console] Make sure signals registered by `SignalableCommandInterface` commands are defined in the PCNTL extension
I think we should not enforce something that PHP allow. So :+1: with checking only if the number is lower than 65
I think we should not enforce something that PHP allow. So +1 with checking only if the number is lower than 65
[Console] Make sure signals registered by `SignalableCommandInterface` commands are defined in the PCNTL extension
I think we should not enforce something that PHP allow. So :+1: with checking only if the number is lower than 65
[Console] Make sure signals registered by `SignalableCommandInterface` commands are defined in the PCNTL extension
I think we should not enforce something that PHP allow. So :+1: with checking only if the number is lower than 65
Upgrade to sF 6.2
Modernize the codebase + fix some wording
Merge pull request #15 from lyrixx/update
update
Correction
[Console] Make sure signals registered by `SignalableCommandInterface` commands are defined in the PCNTL extension
Are we sure the signal list is finite?
Use M1 compatible base images?
On some projects we have to add this to our Docker Compose files (platform: linux/amd64);
version: '3.7'
volumes:
builder-data: {}
services:
php-base:
build: services/php-base
platform: linux/amd64
builder:
build: services/builder
platform: linux/amd64
To allow Macbooks with M1 chips to build.
It run but then it's painfully slow.
Could it be that our base images are not M1 compatible? Could we found images that runs anywhere?
Use M1 compatible base images?
Closing for lack of activity
New PasswordStrength constraint
We have something really similar in our application, so I think it's a good idea to have this feature in the core
slow when profiler is disabled
Hello,
Symfony 3.4 is is not maintained anymore. I strongly suggest you to upgrade as soon as possible.
Then, the profiler should be used only in dev. It's disabled by default in production environment. IMHO disabling it in all environment doesn't increase the security but it decrease for sure the DX
[HttpClient] Add hint about `max_duration` option
Good catch! What about updating all other duration too?
lyrixx push lyrixx/symfony
Update src/Symfony/Component/Console/Command/DumpCompletionCommand.php
