Fix Typo in Http Client

.doctor-rst.yaml

@@ -40,18 +40,18 @@ rules:
     extend_abstract_controller: ~
 #    no_app_bundle: ~
 
-    #   4.x
+    #   master
     versionadded_directive_major_version:
-        major_version: 4
+        major_version: 5
 
     versionadded_directive_min_version:
-        min_version: '4.0'
+        min_version: '5.0'
 
     deprecated_directive_major_version:
-        major_version: 4
+        major_version: 5
 
     deprecated_directive_min_version:
-        min_version: '4.0'
+        min_version: '5.0'
 
 # do not report as violation
 whitelist:
@@ -80,8 +80,12 @@ whitelist:
         - '.. versionadded:: 1.6' # Flex in setup/upgrade_minor.rst
         - '0 => 123' # assertion for var_dumper - components/var_dumper.rst
         - '1 => "foo"' # assertion for var_dumper - components/var_dumper.rst
+        - '123,' # assertion for var_dumper - components/var_dumper.rst
+        - '"foo",' # assertion for var_dumper - components/var_dumper.rst
         - '$var .= "Because of this `\xE9` octet (\\xE9),\n";'
         - "`Deploying Symfony 4 Apps on Heroku`_."
         - ".. _`Deploying Symfony 4 Apps on Heroku`: https://devcenter.heroku.com/articles/deploying-symfony4"
+        - "//                  224, 165, 141, 224, 164, 164, 224, 165, 135])"
         - '.. versionadded:: 0.2' # MercureBundle
+        - 'provides a ``loginUser()`` method to simulate logging in in your functional'
         - '.. code-block:: twig'

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,7 +1,7 @@
 <!--
 
 If your pull request fixes a BUG, use the oldest maintained branch that contains
-the bug (see https://symfony.com/roadmap for the list of maintained branches).
+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 `master` for features of unreleased versions).

_build/redirection_map

@@ -429,6 +429,7 @@
 /profiler/storage /profiler
 /setup/composer /setup
 /security/security_checker /setup
+/setup/built_in_web_server /setup/symfony_server
 /service_container/parameters /configuration
 /routing/generate_url_javascript /routing
 /routing/slash_in_parameter /routing
@@ -478,6 +479,7 @@
 /components/translation/usage /translation
 /components/translation/custom_formats https://github.com/symfony/translation
 /components/translation/custom_message_formatter https://github.com/symfony/translation
+/components/notifier https://github.com/symfony/notifier
 /components/routing https://github.com/symfony/routing
 /doctrine/pdo_session_storage /session/database
 /doctrine/mongodb_session_storage /session/database

bundles/configuration.rst

@@ -199,10 +199,6 @@ The ``Configuration`` class to handle the sample configuration looks like::
         }
     }
 
-.. deprecated:: 4.2
-
-    Not passing the root node name to ``TreeBuilder`` was deprecated in Symfony 4.2.
-
 .. seealso::
 
     The ``Configuration`` class can be much more complicated than shown here,

cache.rst

@@ -30,10 +30,6 @@ The following example shows a typical usage of the cache::
 Symfony supports Cache Contracts, PSR-6/16 and Doctrine Cache interfaces.
 You can read more about these at the :doc:`component documentation </components/cache>`.
 
-.. versionadded:: 4.2
-
-    The cache contracts were introduced in Symfony 4.2.
-
 .. _cache-configuration-with-frameworkbundle:
 
 Configuring Cache with FrameworkBundle
@@ -432,10 +428,6 @@ If an error happens when storing an item in a pool, Symfony stores it in the
 other pools and no exception is thrown. Later, when the item is retrieved,
 Symfony stores the item automatically in all the missing pools.
 
-.. versionadded:: 4.4
-
-    Support for configuring a chain using ``framework.cache.pools`` was introduced in Symfony 4.4.
-
 .. configuration-block::
 
     .. code-block:: yaml
@@ -661,10 +653,6 @@ To see all available cache pools:
 
     $ php bin/console cache:pool:list
 
-.. versionadded:: 4.3
-
-    The ``cache:pool:list`` command was introduced in Symfony 4.3.
-
 Clear one pool:
 
 .. code-block:: terminal

components/asset.rst

@@ -165,6 +165,22 @@ In those cases, use the
     echo $package->getUrl('css/app.css');
     // result: build/css/app.b916426ea1d10021f3f17ce8031f93c2.css
 
+If your JSON file is not on your local filesystem but is accessible over HTTP,
+use the :class:`Symfony\\Component\\Asset\\VersionStrategy\\RemoteJsonManifestVersionStrategy`
+with the :doc:`HttpClient component </http_client>`::
+
+    use Symfony\Component\Asset\Package;
+    use Symfony\Component\Asset\VersionStrategy\RemoteJsonManifestVersionStrategy;
+    use Symfony\Component\HttpClient\HttpClient;
+
+    $httpClient = HttpClient::create();
+    $manifestUrl = 'https://cdn.example.com/rev-manifest.json';
+    $package = new Package(new RemoteJsonManifestVersionStrategy($manifestUrl, $httpClient));
+
+.. versionadded:: 5.1
+
+    The ``RemoteJsonManifestVersionStrategy`` was introduced in Symfony 5.1.
+
 Custom Version Strategies
 .........................
 

components/browser_kit.rst

@@ -40,13 +40,7 @@ The component only provides an abstract client and does not provide any backend
 ready to use for the HTTP layer. To create your own client, you must extend the
 ``AbstractBrowser`` class and implement the
 :method:`Symfony\\Component\\BrowserKit\\AbstractBrowser::doRequest` method.
-
-.. deprecated:: 4.3
-
-    In Symfony 4.3 and earlier versions, the ``AbstractBrowser`` class was called
-    ``Client`` (which is now deprecated).
-
-The ``doRequest()`` method accepts a request and should return a response::
+This method accepts a request and should return a response::
 
     namespace Acme;
 
@@ -317,10 +311,6 @@ dedicated web crawler or scraper such as `Goutte`_::
         '.table-list-header-toggle a:nth-child(1)'
     )->text());
 
-.. versionadded:: 4.3
-
-    The feature to make external HTTP requests was introduced in Symfony 4.3.
-
 Learn more
 ----------
 

components/cache/adapters/array_cache_adapter.rst

@@ -8,10 +8,7 @@ Array Cache Adapter
 Generally, this adapter is useful for testing purposes, as its contents are stored in memory
 and not persisted outside the running PHP process in any way. It can also be useful while
 warming up caches, due to the :method:`Symfony\\Component\\Cache\\Adapter\\ArrayAdapter::getValues`
-method.
-
-This adapter can be passed a default cache lifetime as its first parameter, and a boolean that
-toggles serialization as its second parameter::
+method::
 
     use Symfony\Component\Cache\Adapter\ArrayAdapter;
 
@@ -23,5 +20,17 @@ toggles serialization as its second parameter::
         $defaultLifetime = 0,
 
         // if ``true``, the values saved in the cache are serialized before storing them
-        $storeSerialized = true
+        $storeSerialized = true,
+
+        // the maximum lifetime (in seconds) of the entire cache (after this time, the
+        // entire cache is deleted to avoid stale data from consuming memory)
+        $maxLifetime = 0,
+
+        // the maximum number of items that can be stored in the cache. When the limit
+        // is reached, cache follows the LRU model (least recently used items are deleted)
+        $maxItems = 0
     );
+
+.. versionadded:: 5.1
+
+    The ``maxLifetime`` and ``maxItems`` options were introduced in Symfony 5.1.

components/cache/adapters/couchbasebucket_adapter.rst

@@ -0,0 +1,150 @@
+.. index::
+    single: Cache Pool
+    single: Couchabase Cache
+
+.. _couchbase-adapter:
+
+Couchbase Cache Adapter
+=======================
+
+.. versionadded:: 5.1
+
+    The CouchbaseBucketAdapter was introduced in Symfony 5.1.
+
+This adapter stores the values in-memory using one (or more) `Couchbase server`_
+instances. Unlike the :ref:`APCu adapter <apcu-adapter>`, and similarly to the
+:ref:`Memcached adapter <memcached-adapter>`, it is not limited to the current server's
+shared memory; you can store contents independent of your PHP environment.
+The ability to utilize a cluster of servers to provide redundancy and/or fail-over
+is also available.
+
+.. caution::
+
+    **Requirements:** The `Couchbase PHP extension`_ as well as a `Couchbase server`_
+    must be installed, active, and running to use this adapter. Version ``2.6`` or
+    greater of the `Couchbase PHP extension`_ is required for this adapter.
+
+This adapter expects a `Couchbase Bucket`_ instance to be passed as the first
+parameter. A namespace and default cache lifetime can optionally be passed as
+the second and third parameters::
+
+    use Symfony\Component\Cache\Adapter\CouchbaseBucketAdapter;
+
+    $cache = new CouchbaseBucketAdapter(
+        // the client object that sets options and adds the server instance(s)
+        \CouchbaseBucket $client,
+
+        // the name of bucket
+        string $bucket,
+
+        // a string prefixed to the keys of the items stored in this cache
+        $namespace = '',
+
+        // the default lifetime (in seconds) for cache items that do not define their
+        // own lifetime, with a value 0 causing items to be stored indefinitely
+        $defaultLifetime = 0,
+    );
+
+
+Configure the Connection
+------------------------
+
+The :method:`Symfony\\Component\\Cache\\Adapter\\CouchbaseBucketAdapter::createConnection`
+helper method allows creating and configuring a `Couchbase Bucket`_ class instance using a
+`Data Source Name (DSN)`_ or an array of DSNs::
+
+    use Symfony\Component\Cache\Adapter\CouchbaseBucketAdapter;
+
+    // pass a single DSN string to register a single server with the client
+    $client = CouchbaseBucketAdapter::createConnection(
+        'couchbase://localhost'
+        // the DSN can include config options (pass them as a query string):
+        // 'couchbase://localhost:11210?operationTimeout=10'
+        // 'couchbase://localhost:11210?operationTimeout=10&configTimout=20'
+    );
+
+    // pass an array of DSN strings to register multiple servers with the client
+    $client = CouchbaseBucketAdapter::createConnection([
+        'couchbase://10.0.0.100',
+        'couchbase://10.0.0.101',
+        'couchbase://10.0.0.102',
+        // etc...
+    ]);
+
+    // a single DSN can define multiple servers using the following syntax:
+    // host[hostname-or-IP:port] (where port is optional). Sockets must include a trailing ':'
+    $client = CouchbaseBucketAdapter::createConnection(
+        'couchbase:?host[localhost]&host[localhost:12345]'
+    );
+
+
+Configure the Options
+---------------------
+
+The :method:`Symfony\\Component\\Cache\\Adapter\\CouchbaseBucketAdapter::createConnection`
+helper method also accepts an array of options as its second argument. The
+expected format is an associative array of ``key => value`` pairs representing
+option names and their respective values::
+
+    use Symfony\Component\Cache\Adapter\CouchbaseBucketAdapter;
+
+    $client = CouchbaseBucketAdapter::createConnection(
+        // a DSN string or an array of DSN strings
+        [],
+
+        // associative array of configuration options
+        [
+            'username' => 'xxxxxx',
+            'password' => 'yyyyyy',
+            'configTimeout' => '100',
+        ]
+    );
+
+Available Options
+~~~~~~~~~~~~~~~~~
+
+``username`` (type: ``string``)
+    Username for connection ``CouchbaseCluster``.
+
+``password`` (type: ``string``)
+    Password of connection ``CouchbaseCluster``.
+
+``operationTimeout`` (type: ``int``, default: ``2500000``)
+    The operation timeout (in microseconds) is the maximum amount of time the library will
+    wait for an operation to receive a response before invoking its callback with a failure status.
+
+``configTimeout`` (type: ``int``, default: ``5000000``)
+    How long (in microseconds) the client will wait to obtain the initial configuration.
+
+``configNodeTimeout`` (type: ``int``, default: ``2000000``)
+    Per-node configuration timeout (in microseconds).
+
+``viewTimeout`` (type: ``int``, default: ``75000000``)
+    The I/O timeout (in microseconds) for HTTP requests to Couchbase Views API.
+
+``httpTimeout`` (type: ``int``, default: ``75000000``)
+    The I/O timeout (in microseconds) for HTTP queries (management API).
+
+``configDelay`` (type: ``int``, default: ``10000``)
+    Config refresh throttling
+    Modify the amount of time (in microseconds) before the configuration error threshold will forcefully be set to its maximum number forcing a configuration refresh.
+
+``htconfigIdleTimeout`` (type: ``int``, default: ``4294967295``)
+    Idling/Persistence for HTTP bootstrap (in microseconds).
+
+``durabilityInterval`` (type: ``int``, default: ``100000``)
+    The time (in microseconds) the client will wait between repeated probes to a given server.
+
+``durabilityTimeout`` (type: ``int``, default: ``5000000``)
+    The time (in microseconds) the client will spend sending repeated probes to a given key's vBucket masters and replicas before they are deemed not to have satisfied the durability requirements.
+
+.. tip::
+
+    Reference the `Couchbase Bucket`_ extension's `predefined constants`_ documentation
+    for additional information about the available options.
+
+.. _`Couchbase PHP extension`: https://docs.couchbase.com/sdk-api/couchbase-php-client-2.6.0/files/couchbase.html
+.. _`predefined constants`: https://docs.couchbase.com/sdk-api/couchbase-php-client-2.6.0/classes/Couchbase.Bucket.html
+.. _`Couchbase server`: https://couchbase.com/
+.. _`Couchbase Bucket`: https://docs.couchbase.com/sdk-api/couchbase-php-client-2.6.0/classes/Couchbase.Bucket.html
+.. _`Data Source Name (DSN)`: https://en.wikipedia.org/wiki/Data_source_name

components/cache/adapters/memcached_adapter.rst

@@ -70,10 +70,6 @@ helper method allows creating and configuring a `Memcached`_ class instance usin
         'memcached:?host[localhost]&host[localhost:12345]&host[/some/memcached.sock:]=3'
     );
 
-.. versionadded:: 4.2
-
-    The option to define multiple servers in a single DSN was introduced in Symfony 4.2.
-
 The `Data Source Name (DSN)`_ for this adapter must use the following format:
 
 .. code-block:: text

components/cache/adapters/redis_adapter.rst

@@ -102,14 +102,6 @@ name of your service group::
         'redis:?host[redis1:26379]&host[redis2:26379]&host[redis3:26379]&redis_sentinel=mymaster'
     );
 
-.. versionadded:: 4.2
-
-    The option to define multiple servers in a single DSN was introduced in Symfony 4.2.
-
-.. versionadded:: 4.4
-
-    Redis Sentinel support was introduced in Symfony 4.4.
-
 .. note::
 
     See the :class:`Symfony\\Component\\Cache\\Traits\\RedisTrait` for more options

components/cache/psr6_psr16_adapters.rst

@@ -46,10 +46,6 @@ this use-case::
     // now use this wherever you want
     $githubApiClient = new GitHubApiClient($psr6Cache);
 
-.. versionadded:: 4.3
-
-    The ``Psr16Adapter`` class was introduced in Symfony 4.3.
-
 Using a PSR-6 Cache Object as a PSR-16 Cache
 --------------------------------------------
 
@@ -87,8 +83,4 @@ this use-case::
     // now use this wherever you want
     $githubApiClient = new GitHubApiClient($psr16Cache);
 
-.. versionadded:: 4.3
-
-    The ``Psr16Cache`` class was introduced in Symfony 4.3.
-
 .. _`PSR-16`: https://www.php-fig.org/psr/psr-16/