@@ -134,8 +134,8 @@ is thrown if an unknown option is passed::
134
134
'usernme' => 'johndoe',
135
135
));
136
136
137
- // UndefinedOptionsException: The option "usernme" does not exist. Known
138
- // options are: "host", "password", "port", "username"
137
+ // UndefinedOptionsException: The option "usernme" does not exist.
138
+ // Known options are: "host", "password", "port", "username"
139
139
140
140
The rest of your code can access the values of the options without boilerplate
141
141
code::
@@ -354,8 +354,8 @@ is thrown::
354
354
'host' => 25,
355
355
));
356
356
357
- // InvalidOptionsException: The option "host" with value "25" is expected to
358
- // be of type "string"
357
+ // InvalidOptionsException: The option "host" with value "25" is
358
+ // expected to be of type "string"
359
359
360
360
In sub-classes, you can use :method: `Symfony\\ Component\\ OptionsResolver\\ OptionsResolver::addAllowedTypes `
361
361
to add additional allowed types without erasing the ones already set.
@@ -395,8 +395,8 @@ is thrown::
395
395
'transport' => 'send-mail',
396
396
));
397
397
398
- // InvalidOptionsException: The option "transport" has the value "send-mail",
399
- // but is expected to be one of "sendmail", "mail", "smtp"
398
+ // InvalidOptionsException: The option "transport" has the value
399
+ // "send-mail", but is expected to be one of "sendmail", "mail", "smtp"
400
400
401
401
For options with more complicated validation schemes, pass a closure which
402
402
returns ``true `` for acceptable values and ``false `` for invalid values::
0 commit comments