[Form] Changed Form::getErrors() to return an iterator and added two optional parameters $deep and $flatten
[Form] Changed the default value of $flatten in Form::getErrors() to true
Add class constants for access decision strategies.
[Validator] Checked the constraint class in constraint validators
feature #9918 [Form] Changed Form::getErrors() to return an iterator and added two optional parameters $deep and $flatten (webmozart)

This PR was merged into the 2.5-dev branch.

Discussion
----------

[Form] Changed Form::getErrors() to return an iterator and added two optional parameters $deep and $flatten

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | yes
| BC breaks?    | yes
| Deprecations? | yes
| Tests pass?   | yes
| Fixed tickets | #7205
| License       | MIT
| Doc PR        | -

See the changes in the UPGRADE files for more information.

Commits
-------

6b3fbb5 [Form] Changed the default value of $flatten in Form::getErrors() to true
a9268c4 [Form] Changed Form::getErrors() to return an iterator and added two optional parameters $deep and $flatten
feature #10414 [Validator] Checked the constraint class in constraint validators (webmozart)

This PR was merged into the 2.5-dev branch.

Discussion
----------

[Validator] Checked the constraint class in constraint validators

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | -
| License       | MIT
| Doc PR        | -

Commits
-------

df56c23 [Validator] Checked the constraint class in constraint validators
[Form] Removed "magic" from FormErrorIterator
feature #10418 [Form] Removed "magic" from FormErrorIterator (webmozart)

This PR was merged into the 2.5-dev branch.

Discussion
----------

[Form] Removed "magic" from FormErrorIterator

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | -
| License       | MIT
| Doc PR        | -

Commits
-------

daac66e [Form] Removed "magic" from FormErrorIterator
[Process] Add Process::disableOutput and Process::enableOutput methods
feature #10425 [Process] Add Process::disableOutput and Process::enableOutput methods (romainneutron)

This PR was merged into the 2.5-dev branch.

Discussion
----------

[Process] Add Process::disableOutput and Process::enableOutput methods

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | yes
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #9007
| License       | MIT
| Doc PR        | https://github.com/symfony/symfony-docs/pull/3664

This is another implementation for #9007 that allows to disable the output/error-output storage in a Process in order to avoid using memory.
This is particularly useful when the process outputs large data and it's not read.

Commits
-------

a891e14 [Process] Add Process::disableOutput and Process::enableOutput methods
minor #10432 clean up framework bundle commands (cordoval)

This PR was merged into the 2.5-dev branch.

Discussion
----------

clean up framework bundle commands

|Q            |A  |
|---          |---|
|Bug Fix?     |no |
|New Feature? |no |
|BC Breaks?   |no |
|Deprecations?|no |
|Tests Pass?  |yes|
|Fixed Tickets|   |
|License      |MIT|
|Doc PR       |na |

Commits
-------

0984313 clean up commands from framework bundle
minor #10390 [Security] Add constants for access decision strategies (c960657)

This PR was merged into the 2.5-dev branch.

Discussion
----------

[Security] Add constants for access decision strategies

I suggest adding constants for the three access decision strategies (affirmative, consensus, unanimous).

They are difficult to spell, and without constants they are difficult to identify when reading the code.

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | yes
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | N/A
| License       | MIT
| Doc PR        | N/A

Commits
-------

5d6ef00 Add class constants for access decision strategies.
[SecurityBundle] changed a hardcoded string to its constant equivalent
[FrameworkBundle] Add posibility to specify method and host in router:match command
feature #10439 [FrameworkBundle] Add posibility to specify method and host in router:match command (romainneutron)

This PR was merged into the 2.5-dev branch.

Discussion
----------

[FrameworkBundle] Add posibility to specify method and host in router:match command

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | yes
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| License       | MIT

Replaces #9340

Commits
-------

acc66b9 [FrameworkBundle] Add posibility to specify method and host in router:match command
[FrameworkBundle] Use DIC parameter as default host value if available
bug #10443 [FrameworkBundle] Use DIC parameter as default host value if available (romainneutron)

This PR was merged into the 2.5-dev branch.

Discussion
----------

[FrameworkBundle] Use DIC parameter as default host value if available

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| License       | MIT

This follows #10439

Commits
-------

85a2fbf [FrameworkBundle] Use DIC parameter as default host value if available
tweaked sentence
Make it possible to match the request based on HTTP methods in the firewall configuration
feature #10404 [Security] Match request based on HTTP methods in firewall config (danez)

This PR was submitted for the 2.4 branch but it was merged into the 2.5-dev branch instead (closes #10404).

Discussion
----------

[Security] Match request based on HTTP methods in firewall config

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | yes
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets |
| License       | MIT
| Doc PR        | symfony/symfony-docs#3681

For an api I had to work on, I was in the need to have different firewalls for different HTTP Methods. I started building my own ```RequestMatcher``` until I discovered, that the regular RequestMatcher is able to handle HTTP Methods. The only thing that is missing is the possibility to configure it in the firewall section of the configuration. (For access_control it is already possible)

With this PR it is possible to do things like this:
```yaml
security:
    firewalls:
        api_options:
            pattern:    ^/
            methods:    [OPTIONS]
            security:   false
        api:
            pattern:    ^/
            some_auth:  true
```

I think this integrates quite nicely. Or is there any downside you can think of?

If it is good to go, I'll open a PR for the docs.

Commits
-------

2878757 Make it possible to match the request based on HTTP methods in the firewall configuration