-
Notifications
You must be signed in to change notification settings - Fork 621
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[plain JS] templateUrl not working with short path #1901
Comments
This is not expected behaviour, because @Component({
moduleId: module.id,
...
}) |
@ardatan Thank you! It works fine now. I had to add it on any component where a short path is used. Same thing with the pathes to scss files. PS. I updated my previous post with error messages displayed on the browser console after a very long time. |
I think there is a wrong path in a source file, because when there is one, it sends index.html as default for 404. After that, this causes recursion by bootstrapping app again and again ( we couldn't find a proper way to handle this ). |
I checked all of the 5 pathes of html and scss files existing in the code of atao60/meteor-angular-ionic: there are all fine. AFAIU, no needs to search for a wrong path. Even if it seems Angular doesn't promote anymore the usage of 'moduleId', it's well documented, see e.g. Component-Relative Paths in Angular which among others states:
that is exactly the observed behavior. As I'm happy with the moduleId workaround, do we need to keep the present issue open? |
Thank you for your collaboration! |
When reporting a bug, please be sure to include the following:
angular-meteor
you're using, and the platform(s) you're running it onbug?
A working demo is available on atao60/meteor-angular-ionic. This demo is based on Angular Meteor bare. All the code (but the tests) is in plain JS, even the annotations (Component, NgModule,...)
As soon as a path such as:
templateUrl: 'client/imports/app/app.html'
is replaced by:
templateUrl: 'app.html'
the associated part of the view isn't correctly displayed.
Is this the expected behavior with vanilla JS w/o "@" annotations, ie full pathes required?
Should it be possible to keep the same behavior than with TS and "@" annotations, ie short pathes accepted?
dev config
UPDATE
After a very long time, error messages are displayed on the browser console:
The text was updated successfully, but these errors were encountered: