9

So I been started using ES6 in Meteor, but apparently if you try to use Meteor.publish syntax with an arrow function, this.userId is undefined, while if you use it with a regular function(){} this.userId works perfectly, Im assuming is a kind of transpiler process that assign a different this, to userId but is just a guess, does anyone knows what really is happening?

Meteor.startup(function() {
    Meteor.publish("Activities", function() { //with function
        console.log(this.userId); //TS8vTE3z56LLcaCb5
    });
});

Meteor.startup(function() {
    Meteor.publish("Activities", ()=> { //with arrow function
        console.log(this.userId); //undefined
    });
});
ncubica
  • 8,169
  • 9
  • 54
  • 72
  • From MDN: *"An arrow function expression (also known as fat arrow function) has a shorter syntax compared to function expressions and **lexically binds the `this` value**.'* https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions – Felix Kling Oct 10 '15 at 17:49
  • @FelixKling how this is a duplicate question? – ncubica Oct 10 '15 at 18:52
  • It exaplains how `this` in arrow functions works. – Felix Kling Oct 10 '15 at 18:52
  • 1
    @FelixKling arrow function is specific in the context of ES6, while I understand your point I think that answer is not broad enough to understand that concept from Meteor perspective, you should reevaluate your decision IMHO. – ncubica Jul 06 '16 at 21:51

1 Answers1

7

This isn't a transpilation error, it's a feature of arrow functions. The arrow function automatically sets the context of the function body to the contexts here it was created, in this case the callback to Meteor.publish. This prevents Meteor from rebinding the context of your listener function.

From the Meteor publish docs:

Inside the function, this is the publish handler object

If you want things to work properly you will need to use the "old-school" function syntax to allow Meteor to set the context properly.

Nick Tomlin
  • 28,402
  • 11
  • 61
  • 90