peerlibrary / meteor-publish-context

Provide DDP._CurrentPublish with access to current publish context

DDP._CurrentPublish with current publish context

Adding this package to your Meteor application creates a DDP._CurrentPublish environment variable which you can use to access current publish context (this inside publish function) from anywhere in the server-side code, if that server-side code was called from a publish function.

It is similar to existing undocumented DDP._CurrentInvocation which does the same for method calls, giving you access to the current context of a method call (this inside a method's body).

Not needed with Meteor >= 1.5.1. There is DDP._CurrentPublicationInvocation now available, and DDP._CurrentInvocation has been renamed to DDP._CurrentMethodInvocation. This package provides the same functionality for previous Meteor versions.

Server side only.

Installation

meteor add peerlibrary:publish-context

After adding the package, you have to depend on, or import, Meteor's core ddp package to get access to the DDP symbol.

Examples

Implementing a userId() function on the server-side, which works in any code called from methods or publish functions, can then be simply implemented as:

function userId() {
  const currentInvocation = DDP._CurrentInvocation.get();
  if (currentInvocation) return currentInvocation.userId;

  const currentContext = DDP._CurrentPublish.get();
  if (currentContext) return currentContext.userId;

  throw new Error("userId() not invoked from a method or publish function.");
}

This is more or less what peerlibrary:user-extra package does to provide Meteor.userId().

meteor-publish-context's Issues

It does not work for the automated publications for users

I20180109-18:04:02.592(2)? no invoke, CursorDescription {
I20180109-18:04:02.592(2)?   collectionName: 'users',
I20180109-18:04:02.592(2)?   selector: { _id: 'jzsdfPdbjBMdAedPg' },
I20180109-18:04:02.592(2)?   options:
I20180109-18:04:02.592(2)?    { transform: null,
I20180109-18:04:02.592(2)?      fields: { profile: 1, username: 1, emails: 1 } } }```

When that publication entry is created it does not put it inside DDP._CurrentPublish.get()

Any clues why ?

Publish override might be incomplete

I just had a look at the Meteor.publish override code and it looks like it doesn't take the following format of Meteor.publish into account.

Meteor.publish({
  allPosts() {
    const userId = this.userId;
    return userId ? Posts.find({ userId }) : this.ready();
});

Just as with Meteor.methods, Meteor.publish allows the developer to give it an object.