typeahead typeahead-input-formatter fails when promise is returned

[pdanpdan]

Hello.

There is a problem with typeahead when the typeahead-input-formatter returns a promise, as the model.$formatters chain does not support promises.

I was able to bypass this by this ugly hack:

modelCtrl.$formatters.push(function (modelValue) {

        var candidateViewValue, emptyViewValue;
        var locals = {};

        if (inputFormatter) {

          locals['$model'] = modelValue;
--          return inputFormatter(originalScope, locals);

++          $q.when(inputFormatter(originalScope, locals))
++            .then(function(viewValue) {
++              modelCtrl.$viewValue = viewValue;
++              modelCtrl.$render();
++            });
++          return modelCtrl.$viewValue;

        } else {

But this bypasses the $formatters chain completely.
The only real solution I see is to replace the angular $formatters processing chain to use promises.

[pkozlowski-opensource]

@pdanpdan what is your use case?

[chrisirhc]

#888 supports promises through the queryParsers API. I'm still wondering whether it's a good idea. ngModel's $formatters/$parsers doesn't currently support promises.
It'll be good to understand @pdanpdan's use case. What I thought of so far is just server-side validation.

[pdanpdan]

http://plnkr.co/edit/bf3SPRre99Qbsx574Nnq?p=preview

[pkozlowski-opensource]

@chrisirhc yeh, async formatters are tricky business.... I'm not super-clear on supporting them...

[natcohen]

Anything about this?

[rvanbaalen]

Closing this due to inactivity. I'm thinking something similar could be achieved by (ab)using the $asyncValidators pipeline in Angular 1.3 these days? But that's just a wild guess and you'll probably be using the validator pipeline for formatting purposes in that case which smells bad.