Tomasz Pluskiewicz

Turns out it's something that StructureMap does but not TinyIoC...

Have to consider twice. Not all would possibly be injected in the same scope. Maybe this should actually stay the API's responsibility to register.

Hi. Thank you so much for taking your time to investigate thoroughly. Unfortunately though your suggestions did not help me. I will try to compile a minimal reproduction for you...

Sure, I just pushed latest changes. In fact something changed and now I'm seeing this same error even in unbundled build. Hell, even in simple `polymer serve` :(. No cache,...

OIC! It started ocurring in unminified from when I added `firebase-*` elements to fragments in polymer.json. When minified, I indeed had to additionally apply your solution to overcome the compute...

I'm implementing a JS-only client and a Hydra console as playground On Aug 23, 2016, 21:38, at 21:38, Markus Lanthaler [email protected] wrote: > Sure, for what though? :-) > >...

Oh, sorry, you're right. Of course, this was meant for the demo API repository

Which I don't see by the way in your repo list...

To fix it in HydraBundle, it would have to be configurable. After all, not everyone will want to publish their API publicly for everyone. So, would you like me to...

Unfortunately EAP 3 doesn't work either :(. Same error.