Denis Zhbankov

It is, but additional https server instance has to be created. PRs are welcome )

Hi! At first glance, seems like some changes are actually required (at least for optimisation). I'll do them when I have time.

I've looked at it again and it's not a question of optimisation. AngularEvaporate shouldn't work with evaporate@2 without any modifications (and also these modifications, probably, wouldn't be backwards compatible). So...

So the directive is only a template?

PRs are always welcome)

Well, `$rinserepeat` option does exactly what the readme says: it cleans an input after every selection. Can't really reproduce any bugs, for me it works as expected. If for you...

Hi! Could you please clarify a little more? I don't really understand what do you want to achieve.

1. The necessity of automatic `$dequeue()` when completed is debatable for me. Probably somebody would want the opposite if we changed this behaviour. 2. But I'm worried about the `$stopped`...

1. Ok, now I got it. You're talking about some new flag, like `$rinserepeat`, for a directive, right? Probably a good idea, worth to be considered at least. I'll tag...

Well, the callbacks are fired by `Evaporate` itself, whereas `AngularEvaporate` just wraps them to implicitly save timestamps, messages and some other similar stuff. So in case of their odd behaviour...