2 ms·

that work is handled by Aurelia itself. You don't explicitly need to define the element. http://aurelia.io/hub.html#/doc/article/aurelia/framework/latest/creat

by kensign 10y ago

that work is handled by Aurelia itself. You don't explicitly need to define the element. http://aurelia.io/hub.html#/doc/article/aurelia/framework/latest/creating-components/1 http://aurelia.io/hub.html#/doc/article/aurelia/framework/la...

spankalee 10y ago
Sorry, I still don't get it. Take the CustomerDetail example in the "Component Instantiation Through Dependency Injection" section: @inject(HttpClient) export class CustomerDetail { constructor(http) { this.http = http; } } If this really creates a Web Component, how does `this.http` ever get set? The browser will call the constructor with no arguments. What exactly gets passed to `document.registerElement()` (for the v0 Custom Elements API) or `customElements.define()` (for the v1 Custom Elements API)? Are you saying that Aurelia generates and registers a separate custom element class? That's not in the docs. If so, how does that element find the instances to inject into the user-defined constructors? The main issue that talks about custom element support is still open, and the answer really does seem to be that Aurelia can't create custom elements: https://github.com/aurelia/framework/issues/7 https://github.com/aurelia/framework/issues/7 This unfortunately seems to confirm that Aurelia uses the terminology of Web Components, but doesn't actually use or create real Web Components.
- kensign 10y ago
  yeah... You might want to try it out and read the docs before you make such claims https://github.com/aurelia/web-components https://github.com/aurelia/web-components remember too, the ES6 is transpiled. Also, I am done with the nerd war. If you have questions, use the gitter channel.
  - spankalee 10y ago
    "nerd war"? Wow, good to see you go then. That link you just posted is not contained in any of the docs or links that either you or I posted above. I can't actually find it in the entire documentation hub, so even if I did "read the docs", how was I supposed to find it? Bye.

by kensign 10y ago

spankalee 10y ago

Sorry, I still don't get it. Take the CustomerDetail example in the "Component Instantiation Through Dependency Injection" section: @inject(HttpClient) export class CustomerDetail { constructor(http) { this.http = http; } } If this really creates a Web Component, how does `this.http` ever get set? The browser will call the constructor with no arguments. What exactly gets passed to `document.registerElement()` (for the v0 Custom Elements API) or `customElements.define()` (for the v1 Custom Elements API)? Are you saying that Aurelia generates and registers a separate custom element class? That's not in the docs. If so, how does that element find the instances to inject into the user-defined constructors? The main issue that talks about custom element support is still open, and the answer really does seem to be that Aurelia can't create custom elements: https://github.com/aurelia/framework/issues/7 https://github.com/aurelia/framework/issues/7 This unfortunately seems to confirm that Aurelia uses the terminology of Web Components, but doesn't actually use or create real Web Components.

kensign 10y ago
yeah... You might want to try it out and read the docs before you make such claims https://github.com/aurelia/web-components https://github.com/aurelia/web-components remember too, the ES6 is transpiled. Also, I am done with the nerd war. If you have questions, use the gitter channel.
- spankalee 10y ago
  "nerd war"? Wow, good to see you go then. That link you just posted is not contained in any of the docs or links that either you or I posted above. I can't actually find it in the entire documentation hub, so even if I did "read the docs", how was I supposed to find it? Bye.