Accept HTML only custom element in moduleId RouteConfig

[AbraaoAlves]

I'm submitting a feature request

Expected/desired behavior:

• What is the expected behavior?
  The moduleId should work not just ViewModels, but also HTML only custom elements.

Like tag <require from="my-component.html">, that accept viewModels and Views, moduleId in RouteConfig should accept string like this:

    config.map([
       { route: ['', '/'], moduleId: 'no-selection.html',  title: 'Select'},
       { route: 'contacts/:id',  moduleId: 'contact-detail',  name:'contacts'}  
    ]);

What is the motivation / use case for changing the behavior?
Less is MORE. Write empty class to just route works, should not be the Aurelia way.

[EisenbergEffect]

Closing this as a duplicate. We have a feature tracked to enable "view only" routes. Thanks!

[AbraaoAlves]

@EisenbergEffect any link?

[AbraaoAlves]

I don't find any feature like this. Yes is there #25, but is about layout view-only no page view-only.

Take app-contacts app and put this code on app.js:

config.map([
   { route: ['', '/'], **moduleId: 'no-selection.html',**  title: 'Select'},
   { route: 'contacts/:id',  moduleId: 'contact-detail',  name:'contacts'}  
]);

The aurelia-template-route don't work with moduleId path. But if I make little change on route-loader.js ... It works, not more empty class!!

I want know if a way to do this, without change source code?

[carusology]

I also ran into this limitation. As far I as I can tell, we are required to create an empty view-model to back the view. @EisenbergEffect, can you give us a link to whatever issue is tracking this feature request? The issue @AbraaoAlves referenced, #25, does not appear to be related.

[EisenbergEffect]

I thought we had a feature for this somewhere. Perhaps, I was wrong? I'll re-open this.

[carusology]

@EisenbergEffect k, thanks.

When I attempted to get this to work within the current architecture, I used the my-view.html style of syntax that is referenced in Aurelia Hub for HTML-Only custom elements, but put it in my route config, like so:

export class App {

  configureRouter(config, router) {
    this.router = router;
    config.title = 'Aurelia';

    config.map([
      { route: ['', 'home'], name: 'home', moduleId: './my-view.html' }
    ]);
  }
}

However, this results in the error message "Uncaught (in promise) Error: Cannot find module './my-view'." from webpack. Once I added a blank view-model (which, to be fair, is a single line of code) and removed the *.html suffix in the route config it worked fine.

// filename: my-view.ts
export default class MyView {}

This *.html suffix is the exact approach @AbraaoAlves suggested in his pull request. Did you follow the same deductive path, @AbraaoAlves?

Unfortunately, I keep expecting custom elements and views to behave in a similar fashion, but that expectation is consistently wrong.

[AbraaoAlves]

That's it @carusology, clear like water.
Thanks!

[gheoan]

@EisenbergEffect, @AbraaoAlves I think this can be closed since #50 was merged.