diff --git a/configuration/micro_kernel_trait.rst b/configuration/micro_kernel_trait.rst index e1f833e4d6b..b4daf9f476d 100644 --- a/configuration/micro_kernel_trait.rst +++ b/configuration/micro_kernel_trait.rst @@ -110,7 +110,6 @@ that define your bundles, your services and your routes: is new in Symfony 2.8 and has methods that make adding routes in PHP more fun. You can also load external routing files (shown below). - Advanced Example: Twig, Annotations and the Web Debug Toolbar ------------------------------------------------------------- diff --git a/form/form_customization.rst b/form/form_customization.rst index a5dd16234a4..069eab01ca2 100644 --- a/form/form_customization.rst +++ b/form/form_customization.rst @@ -211,7 +211,7 @@ this folder. In this example, the customized fragment name is ``integer_widget`` because you want to override the HTML ``widget`` for all ``integer`` field types. If you need to customize ``textarea`` fields, you would customize ``textarea_widget``. - + The ``integer`` part comes from the class name: ``IntegerType`` becomes ``integer``, based on a standard. diff --git a/performance.rst b/performance.rst index 528f339464e..6fb336db173 100644 --- a/performance.rst +++ b/performance.rst @@ -133,7 +133,7 @@ If you're using the Standard Distribution, make the following changes:: // app.php // ... - + use Symfony\Component\ClassLoader\ApcClassLoader; // do not use $loader as a variable name here as it would diff --git a/reference/forms/types/datetime.rst b/reference/forms/types/datetime.rst index 0b500e8ad9b..b298b419bcc 100644 --- a/reference/forms/types/datetime.rst +++ b/reference/forms/types/datetime.rst @@ -88,7 +88,7 @@ as a series of ``select`` boxes. When the placeholder value is a string, it will be used as the **blank value** of all select boxes:: use Symfony\Component\Form\Extension\Core\Type\DateTimeType; - + $builder->add('startDateTime', DateTimeType::class, array( 'placeholder' => 'Select a value', )); @@ -97,7 +97,7 @@ Alternatively, you can use an array that configures different placeholder values for the year, month, day, hour, minute and second fields:: use Symfony\Component\Form\Extension\Core\Type\DateTimeType; - + $builder->add('startDateTime', DateTimeType::class, array( 'placeholder' => array( 'year' => 'Year', 'month' => 'Month', 'day' => 'Day', diff --git a/security/custom_authentication_provider.rst b/security/custom_authentication_provider.rst index 52506463804..923da49fc67 100644 --- a/security/custom_authentication_provider.rst +++ b/security/custom_authentication_provider.rst @@ -298,7 +298,7 @@ the ``PasswordDigest`` header value matches with the user's password. you are safe to use it with any PHP version in your Symfony application. In PHP versions prior to 5.6, `Symfony Polyfill`_ (which is included in Symfony) will define the function for you. - + .. versionadded:: 2.8 Symfony Polyfill is included by default since Symfony 2.8. Prior to Symfony 2.8, you have to execute ``composer require symfony/polyfill-php56`` to be able to diff --git a/security/custom_provider.rst b/security/custom_provider.rst index 21c467e7cba..491a93b0cb1 100644 --- a/security/custom_provider.rst +++ b/security/custom_provider.rst @@ -9,7 +9,7 @@ When a user submits a username and password, the authentication layer asks the configured user provider to return a user object for a given username. Symfony then checks whether the password of this user is correct and generates a security token so the user stays authenticated during the current session. -Out of the box, Symfony has four user providers: ``memory``, ``entity``, +Out of the box, Symfony has four user providers: ``memory``, ``entity``, ``ldap`` and ``chain``. In this entry you'll see how you can create your own user provider, which could be useful if your users are accessed via a custom database, a file, or - as shown in this example - a web service. diff --git a/security/guard_authentication.rst b/security/guard_authentication.rst index 668ac9b6638..c5524e71d69 100644 --- a/security/guard_authentication.rst +++ b/security/guard_authentication.rst @@ -422,7 +422,7 @@ Each authenticator needs the following methods: You will still need to active ``remember_me`` under your firewall for it to work. Since this is a stateless API, you do not want to support "remember me" functionality in this example. - + **createAuthenticatedToken(UserInterface $user, string $providerKey)** If you are implementing the :class:`Symfony\\Component\\Security\\Guard\\GuardAuthenticatorInterface` instead of extending the :class:`Symfony\\Component\\Security\\Guard\\AbstractGuardAuthenticator` diff --git a/security/user_checkers.rst b/security/user_checkers.rst index 3baf1b57d62..eefcd667e01 100644 --- a/security/user_checkers.rst +++ b/security/user_checkers.rst @@ -146,7 +146,6 @@ is the service id of your user checker: ), )); - Additional Configurations ------------------------- diff --git a/service_container/scopes.rst b/service_container/scopes.rst index 185d042ce1e..527c1cec0ec 100644 --- a/service_container/scopes.rst +++ b/service_container/scopes.rst @@ -8,7 +8,7 @@ How to Work with Scopes The "container scopes" concept explained in this article has been deprecated in Symfony 2.8 and it will be removed in Symfony 3.0. - + Use the ``request_stack`` service (introduced in Symfony 2.4) instead of the ``request`` service/scope and use the ``shared`` setting (introduced in Symfony 2.8) instead of the ``prototype`` scope