Overview of merged pull requests
The documented feature to override the request method with the POST argument
__method or one of the HTTP headers X-Http-Method-Override or X-Http-Method was accidentally removed in the transition towards PSR-7. This adds it back in by adding a middleware that does the same logic that was removed with the previous Http\Request class.
is_numeric evaluates to true for strings like
"1" therefore the generated code would be missing the quotes
necessary to keep the default argument a string. This causes type errors in the proxy class when the arguments type is
Therefore the check whether an argument value is a string should be done first.
This change could be breaking if no type is used and a method somehow relies on the proxy class turning the argument default into a number.
HttpRequestEngine holds a reference to the “current” http request in each step of the middleware chain.
The internal request engine does not, making it hard to write tests, that predict system behavior.
With this patch you can fetch the current request (and not only the outer most) even in
This makes sure
guzzlehttp/psr7 is will not be used in version with a known
The old .phpstorm.meta.php syntax is deprecated, see https://www.jetbrains.com/help/phpstorm/ide-advanced-metadata.html#legacy-metadata-format-deprecated
Code completion in PhpStorm should still “know” about these:
This cleans up the log messages of the
SessionInterface, to reduce log volume.
- 22-06-21 14:35:46 70133 INFO Session: Started session with id ixadt08m586zKtcJmUTZend6ykWvP9fM.
- [array] =>
packageKey: [string] => Neos.Flow className: [string] => Neos\Flow\Session\Session methodName: [string] => start
22-06-21 14:35:46 70133 INFO Session: Started session with id ixadt08m586zKtcJmUTZend6ykWvP9fM.
No information is lost: The
Session prefix to the log message is the class
name and will already be fully qualified if not within
the package key was hardcoded and the method name is always what the
If you for some reason relied on the log messages having that exact format, you will need to adjust whatever you need to adjust.
The session activity should be logged as before, just less noisy.
I did not create this against 5.3, because, … well. But we could, if you like.