Expose FieldHelper to users about angular-form-for

[bvaughn]

Thank you for filing this (and #42). I'm a little swamped this weekend- and in the middle of a pretty major overhaul (see wip pull request 41) so I may not get around to addressing these until Monday or Tuesday. I hope that's not a major inconvenience!

[r-moeritz]

Not at all and thanks for providing us with what I think is the first decent validation library for ng. Keep up the good work.

[bvaughn]

Got a few moment's break today and re-read this issue. I may be misunderstanding your request, but... why not just use the FieldHelper service directly in your custom field directive? For instance:

angular.module('myApp').directive('myCustomField',
  function(FieldHelper) {
    return {
      require: '^formFor',
      restrict: 'EA',
      templateUrl: 'path/to/template.html',
      scope: {
        attribute: '@'
      },
      link: function($scope, $element, $attributes, formForController) {
        FieldHelper.manageFieldRegistration($scope, formForController);

        // Now your $scope has a 'model' attribute
      }
    };
  });

It's already exposed to the $injector. (That's how the built-in directives are all accessing it.)

[bvaughn]

PS. The how-to create a custom field page now shows how the FieldHelper can be used outside of the formFor project to create a custom input field.

[r-moeritz]

I was getting errors when trying to resolve FieldHelper but I now realize it's because I was using an old version of form-for (1.1.9). After upgrading to 1.2.16 I'm able to use the FieldHelper as you described. Thanks!

[bvaughn]

Ah, excellent. :)

Look for 1.3 soon! ;)