Fixes bug #432. I think it is a fundamental problem that AngularJS doesn't run the formatters unless the $modelValue changes. Meaning that on initialization Angular won't run the formatters. There are some issues open to change how angular handles formatters including a PR (angular/angular.js#10764). Currently I don't see a way to run the formatters without causing a SetDirty event from triggering. The only solution I see is to reset the field controller to pristine after running the formatter the first time.

If someone has a different workaround to this Angular concept I'd love to explore a different solution. -🐙

Author: TheMcMurder

src/directives/formly-field.js

@@ -368,6 +368,7 @@ function formlyField($http, $q, $compile, $templateCache, $interpolate, formlyCo
 
           ctrl.$setViewValue(value);
           ctrl.$render();
+          ctrl.$setPristine();
         }
       }
 

src/directives/formly-field.test.js

@@ -1015,7 +1015,7 @@ describe('formly-field', function() {
         expect(ctrl.$viewValue).to.equal('hello! boo!');
       });
 
-      it(`should format a model value right from the start`, () => {
+      it(`should format a model value right from the start and the form should still be pristine`, () => {
         scope.model = {myKey: 'hello'};
         scope.fields = [getNewField({
           key: 'myKey',
@@ -1026,6 +1026,8 @@ describe('formly-field', function() {
         const ctrl = getNgModelCtrl();
 
         expect(ctrl.$viewValue).to.equal('!hello!');
+        expect(ctrl.$dirty).to.equal(false);
+        expect(ctrl.$pristine).to.equal(true);
       });
 
       it.skip(`should handle multiple form controllers when formatting a model value right from the start`, () => {