- attached 2017-05-09_09-24-32.jpg
Velocity Error: error parsing file template: Unable to find resource 'Lightning File Header.app'
When I try to create a Lightning Component it fails giving me the error: Velocity Error: error parsing file template: Unable to find resource 'Lightning File Header.app'
To recreate I simply go to a project, right click to new lightning component - and error :(
I am able to use Developer Console to create the component and then sync down to Illuminated Cloud and continue development there.
Comments (15)
-
reporter -
repo owner Caleb, are you by chance trying to use a custom template for Lightning components? I ask because I fixed issue
#585in the most recent build which required me to rename the standard header include templates for Lightning markup to make them have unique names ignoring the extension. Can you see if your component template is referencing the correct header? Look in Settings>Editor>File and Code Templates. All of the templates for Lightning components should have the following include:#parse("Lightning Markup File Header.cmp")
Note the
Markup
portion of that name that wasn't there before the most recent build. -
reporter - attached 2017-05-10_17-06-56.jpg
Hm, I don't see that string #parse("Lightning Markup File Header.cmp")
And I found the IlluminatedCloud plugin - Version is 1.7.9.2-idea14
I'm VERY new to IntelliJ so that could also be contributing to the issue.
-
repo owner No problem, Caleb! You're looking at the header but the include will be in the actual file template itself. Switch to Files and take a look at Lightning Component. That should have the
#parse
directive, and my guess is that it's still pointing at the original header. I noticed that in your screenshot some of the templates are blue which means they've been customized (or perhaps that's a side-effect of my change leaving the original templates in-place as if they were made by you), so my guess is that's why this is happening. I might just need to restore the original headers beside the new headers to ensure this doesn't happen to others. -
repo owner Here's a screenshot that might help:
Let me know your findings and I'll be happy to help out.
-
reporter Thanks Scott...here are some screenshots (I may have edited the template, now that you say it I think I had to a while back to make them unique? So maybe I broke it, but I don't really remember :( sorry! makes troubleshooting difficult)
My BLUE ones are: L. Controller has #parse("Lightning File Header JS.js") L. Helper has #parse("Lightning File Header JS.js") L. Renderer has #parse("Lightning File Header JS.js") L. Style has #parse("Lightning File Header CSS.css")
L.Component is #parse("Lightning Markup File Header.cmp")
<aura:component description="${NAME}"> </aura:component>
-
reporter Oh, and I'd be happy to revert to the templates that came with IC if there is a way to do that? I could uninstall & reinstall too :) whatever is easiest, I'll flow.....
-
repo owner Ah, okay. Sounds like you were working around the issue that I fixed. With regard to what you're showing in the latest screenshot, the header name for JS files is
Lightning JS Header File.js
. I think if you move theJS
to match that, it should work.I'm stepping out for dinner so might be delayed on further responses, but let me know if updating things to match the new names doesn't resolve the issue for you.
Also, I don't know if you'll be at Texas Dreamin' tomorrow, but if so we could just sit down together and fix it between sessions.
-
repo owner Regarding reverting, there's a Reset to Default button on the toolbar that you can use to do just that.
-
reporter Awesome. I'm going to test it out now. Yes I'll be at TXD tomorrow, I'll try to track you down if nothing else just to say Hi. Thanks for the quick replies!
-
reporter I reverted to default (i.e. now it says Lightning JS Header File.js) and it worked like a charm! Thank you for the quick resolution and I'm glad it was user error and not a bug in IC!
-
reporter - changed status to resolved
I reverted to default templates for the Lightning JS bits (see full issue thread) and it now all works!
-
repo owner Glad that took care of it! Catch up with you at the Driskill over the next two days.
-
repo owner - changed component to Lightning (Aura)
-
repo owner - changed component to Aura
- Log in to comment