@pkozlowski-opensource you mentioned nearly a month ago that you would release a v0.12.0 with a fix for the typeahead issue. I think this might be the PR you need ;)

any chance this will get merged soon?

(bump) We are having to use my fork because this is not merged.

Landed, thnx so much @zackarychapple !

Just curious why would you make the same request instead of merging the request?

@zackarychapple not sure what you mean... if you look at a0be450 you will notice that it is your commit (that is, you are an author) that was _ committed_ by me. So I didn't do any new request, I've just merged your commit, albeit not using GitHub's merge button but using a technique similar to git cherry picking. Does it clarify things?

@pkozlowski-opensource ahh, fair enough. I was not sure how cherry picks were reflected in github. Is there a benefit to cherry picking on github vs merging PR's? If so I might want to look at doing that on a few repos I commit on.

Any estimates on when 0.12 might be coming as I'm interested in using typeahead with Angular 1.3 RC0 and later without needing to have a manual modification to my angular-ui 0.11 sources that someone might accidentally clobber by updating.

Note: typeahead broke for me with angular 1.3 rc0 -- I forked this repo so I could pull in this fix, and it works fine, but something broke with more recent Angular versions related to $viewValue where it won't display the bound string in the input box, and instead shows [Object object]

Similar issue broke with datepicker