I think this can be added to 2.7 without problems.

@dosten I was thinking it's a BC break because it adds a new method to an interface; any existing code implementing that interface would break unless they implemented this method.

Travis seems to be failing some builds but I think my unit tests are passing.

@colinodell Following the BC promise (http://symfony.com/doc/current/contributing/code/bc.html#changing-interfaces) and as of theFormInterface isn't tagged as@api you can add theclearErrors method without problems.

@dosten: with some problems, check footnote 2:

Should be avoided. When done, this change must be documented in the UPGRADE file.

The required tests now pass after rebasing onto the latestmaster.

I'd prefer to keep this targeted for 3.0/master unless a core dev advises otherwise.

(The BC-break could be avoiding by delaying the interface change until 3.0, but then you'd have to checkmethod_exists on each child which seems too dirty.)

I'm not a fan of adding this method in the FormInterface. It is here for a very specific use case, and this one can already be solved in different ways IMO:#14060

Closing since the original ticket was closed as well:#14060

It was reopened by@fabpot a few days ago though!

@webmozart could you please reopen this?

#14060 has been reopened, and it would be good to have this as an open PR to go with it.

FYI, we cannot reopen the PR as the repository this was based on has been deleted in the meantime.