{"issue":{"title":"NewThreadMessageFormType depends on FOSUserBundle","user":{"login":"jmikola","id":244663,"url":"https://api.github.com/users/jmikola","avatar_url":"https://secure.gravatar.com/avatar/f23700b51dc0c196c1dc02f84aeeecdf?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"f23700b51dc0c196c1dc02f84aeeecdf"},"created_at":"2011-12-29T00:58:37Z","milestone":null,"labels":[],"state":"open","updated_at":"2011-12-29T00:58:37Z","id":2676321,"closed_at":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"html_url":"https://github.com/ornicar/OrnicarMessageBundle/issues/33","body":"According to the docs, FOSUserBundle is an optional dependency; however, the `recipient` field in `NewThreadMessageFormType` depends on the `fos_user_username` field type.\r\n\r\nI found some reference to a FOSUserBundle dependency in #16, but no discussion about it being optional.\r\n\r\n@ornicar: Can you chime in on this? Should NewThreadMessageFormType, as provided by the bundle, support a configurable field type for `recipient`? That seems preferable to having two separate types, one using the FOS field and another a standard text input.","number":33,"url":"https://api.github.com/repos/ornicar/OrnicarMessageBundle/issues/33","comments":0,"assignee":null},"action":"opened"}