-
Notifications
You must be signed in to change notification settings - Fork 26
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
Resolve relative path, not only aside files #65
Comments
If you thing something is wrong you are very much welcome to send a PR. |
Yes, this is definitely an issue when using relative html/css paths in components. For instance, my component looks like this: // app/my-component/my.component.ts
@Component( {
selector: 'my-component',
moduleId: __moduleName,
templateUrl: './my.component.html',
styleUrls: [ './my.component.css' ]
} )
export class MyComponent {} Here, |
Err, never mind, totally missed the |
That's odd. useRelativePaths didn't work for me, setting it to either true or false. |
This solved the problem for me too! |
How to deal with systemjs and module.id property in angular component? Setting UseRelativePaths doesn't help - |
@unsafePtr Make sure |
@gregjacobs Thanks. It was source mistake where is written with big U. May be you can help cause it is a very big headache for me. |
Templates are supposed to be declared relative to the individual folders that the template files are in, whereas this plugin expects them to be declared relative to the root module. That's wrong, and should be fixed.
And yes, UseRelativePaths is set to false and I'm still seeing that behavior. I looked at the code and there's no possible way for it to properly detect the paths of templates in subfolders, relative to their components.
In getFilePath, absPath simply cannot determine the correct relative path. file.path is always the path of app.module.ts, rather than the path of the related component.
The text was updated successfully, but these errors were encountered: