vanilah web component templates

[pragmaproducts]

We have several scenarios where we have custom elements using vanilla web components that do not have a template. The current work around is to just use a empty template so that during the loading process we don't get a error indicating that there must be a template.

Template loading for vanilla web components sound not enforce the presence of a template.
We use this for d3 visualisations where we build up the UI manually.

This issue affects us greatly and we would appreciate any assistance to avoid having to use a empty template tag as that affects content elements.

[StrahilKazlachev]

Does @noView() fit your case?

[pragmaproducts]

since these are frameworkless components using Aurelia framework in it defeats the purpose.
Where in the code base might I find the implementation of @noview perhaps I can find some clues in there

[bigopon]

You can do

export class Ce {
  static $view = null
}

Its a new feature and will take a bit time to get released

[StrahilKazlachev]

@pragmaproducts you lost me, are you wrapping those vanilla components in Aurelia ones or?

[doktordirk]

@pragmaproducts
@noview

templating/src/decorators.js

Line 230 in 2f07382

export function noView(targetOrDependencies?:Function|Array<any>, dependencyBaseUrl?:string): any {

[bigopon]

I guess its the combination of Aurelia life cycle and webcomponent, so the element needs to be registered with both aurelia and customElements registry