Joe Paice
Joe Paice
I just came to try use this extension in one of my shaders and found that I couldn't. Currently I am just exploring WebGL. The particular thing I was trying...
Try using the same clusterId and key pair between devices that you want to connect.
Thanks @vojtajina. I just figured this out yesterday and came to the same conclusion.
What if instead of defining tokens for the custom arguments the injector just concats what is defined in the Inject annotation with the values you pass to the function provided...
@vojtajina I have been thinking of the same solution. +1 for injecting just the value for tokens that are not annotated. For some of the modules I have been writing...
I just got round to trying this out. I like the change. I don't mind having to put the Inject annotation on a provider. I think it makes code more...
What about injecting a config into the HTTP service? ``` javascript export class HTTPConfig { constructor() { } } @Inject(HTTPConfig) export class HTTP { constructor(config) { // do config here...
What happens in the instance where your config depends on the return value of another service? Or if you need a promise to resolve before you can get your config?...
Surely you would have to check the spec if you want to know the properties that you can configure anyway.
I am facing the same issue. I thought it wasn't working either but it turns out it is just taking ~10 seconds to show