Is WebStorm this ignorant of Meteor?

In running an inspection on my Meteor project, WebStorm tells me, “Unresolved variable postTravelWizard” on this line (in a .js file):


Is the problem that WebStorm doesn’t know Meteor well? There is such a “variable” (Template); it’s in the corresponding .html file:

    {{> Template.dynamic template=getStepTemplate}}

You are correct, that’s something JetBrains should know about i.e. can you maybe create an issue as it seems there’s none yet for that problem in particular.

WebStorm could know Meteor better. For example, WebStorm doesn’t recognize some internal packages, such as Check. Also, you need to manually import external packages (should be fixed in the next version).
But when it comes to templates, it works correctly for me…

I did not looked into it deeper, but by default all these {{#each}} etc includes throw error graphics if we keep space between left brackets and word.
Any fast fix ? I want to still have tag pairing of them, just I would love to have {{ #each ...}} instead of {{#each ...}}

I also get with WebStorm “Unused property currentTemplate” with this:

    currentTemplate: function () {
      return Session.get('curTemplate');

Baloney! Or should I say, “bologna” - this code works as intended, and if currentTemplate was unused, it wouldn’t.

I think Re# is the cat’s meow, but as far as Meteor support goes, WebStorm needs to be a little meatier.

I saw what you did there! :laughing:

I don’t.

(need 20 characters)