-
-
Notifications
You must be signed in to change notification settings - Fork 40
Platform specific templateUrls result in ERROR in ENOENT: no such file or directory on these. #75
Comments
There are no plans to support platform-specific templates at the moment. There is an easy workaround though: use the I know this doesn't sound too good, especially since it requires that you modify your app, but I think we should be focusing our effort and limiting support for "extra" features like this one. The plugin has already grown to be very complex and syncing with every ngtools release is very very painful. |
Hey @hdeshev completely understand your position on this.. was just wondering if the same code for styleUrls could be leveraged though to make this quite simple? |
Hey @sis0k0 so this has been resolved for templateUrls? |
Sorry, closed the wrong issue.. |
No worries, was a bit confused after checking the commits. For anyone having this same problem, i just created a bash script to automate changing the filenames back and forth. Works great. |
I agree 100% @EddyVerbruggen |
As I understand it, this plugin now correctly identifies platform specific css, so
welcome.component.ios.css
andwelcome.component.android.css
will be compiled. However in our project we also have platform specific platform templateUrls, sowelcome.component.ios.html
andwelcome.component.android.html
but at present this is resulting inERROR in ENOENT: no such file or directory on these.
Is it possible to get support in place for platform specific templateUrls?
Thanks
The text was updated successfully, but these errors were encountered: