fix:更新已知bug,优化代码
This commit is contained in:
18
vendor/symfony/http-foundation/CHANGELOG.md
vendored
18
vendor/symfony/http-foundation/CHANGELOG.md
vendored
@@ -1,6 +1,24 @@
|
||||
CHANGELOG
|
||||
=========
|
||||
|
||||
6.0
|
||||
---
|
||||
|
||||
* Remove the `NamespacedAttributeBag` class
|
||||
* Removed `Response::create()`, `JsonResponse::create()`,
|
||||
`RedirectResponse::create()`, `StreamedResponse::create()` and
|
||||
`BinaryFileResponse::create()` methods (use `__construct()` instead)
|
||||
* Not passing a `Closure` together with `FILTER_CALLBACK` to `ParameterBag::filter()` throws an `\InvalidArgumentException`; wrap your filter in a closure instead
|
||||
* Not passing a `Closure` together with `FILTER_CALLBACK` to `InputBag::filter()` throws an `\InvalidArgumentException`; wrap your filter in a closure instead
|
||||
* Removed the `Request::HEADER_X_FORWARDED_ALL` constant, use either `Request::HEADER_X_FORWARDED_FOR | Request::HEADER_X_FORWARDED_HOST | Request::HEADER_X_FORWARDED_PORT | Request::HEADER_X_FORWARDED_PROTO` or `Request::HEADER_X_FORWARDED_AWS_ELB` or `Request::HEADER_X_FORWARDED_TRAEFIK`constants instead
|
||||
* Rename `RequestStack::getMasterRequest()` to `getMainRequest()`
|
||||
* Not passing `FILTER_REQUIRE_ARRAY` or `FILTER_FORCE_ARRAY` flags to `InputBag::filter()` when filtering an array will throw `BadRequestException`
|
||||
* Removed the `Request::HEADER_X_FORWARDED_ALL` constant
|
||||
* Retrieving non-scalar values using `InputBag::get()` will throw `BadRequestException` (use `InputBad::all()` instead to retrieve an array)
|
||||
* Passing non-scalar default value as the second argument `InputBag::get()` will throw `\InvalidArgumentException`
|
||||
* Passing non-scalar, non-array value as the second argument `InputBag::set()` will throw `\InvalidArgumentException`
|
||||
* Passing `null` as `$requestIp` to `IpUtils::__checkIp()`, `IpUtils::__checkIp4()` or `IpUtils::__checkIp6()` is not supported anymore.
|
||||
|
||||
5.4
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user