schmittjoh/JMSTranslationBundle — pull request #63 by bvleur (2012-07-28 12:11:22+00:00)
Title: Support translation_domain option on forms

As mentioned in #61, support for the `translation_domain` option should probably be added.

The current commit only supports the `translation_domain` for field specific options.

The form level `translation_domain` option that is set in `setDefaultOptions` isn't parsed yet, but is something I feel we should support. However, as we can't change the domain on a `Message` afterwards, messages can only be created if their domain is known. Therefore we should either do:
* a 2-pass visit (probably a little complex)
* keep all message details locally and create the actual `Message` at the end of visiting the file.

@schmittjoh: What would you think is the best option?

The form level `translation_domain` option that can be inherited from parent forms (see https://github.com/symfony/symfony/pull/4328 ) is probably not something we can statically extract, right?