Server side transform breaks Automatic documents transformation about meteor-astronomy

[lukejagodzinski]

Right now I would discourage you from modifying Astronomy objects on publication. Astronomy objects can't be sent over DDP right now, and I will be working on it soon. It's on my TODO list. Astronomy objects have to EJSONable to allow that. However if you really want to do this there is a way. Here are changes you have to make to your code:

First change is the transform function. I've commented CHANGES.

var transform = function(doc) {
  // YOU HAVE TO GET SIMPLE OBJECT FROM ASTRONOMY OBJECT USING GET() FUNCTION
  var obj = doc.get();

  var lastMessage = Messages.findOne({
    chatId: obj._id
  }, {
    sort: {
      createdAt: -1
    },
    // YOU HAVE TO TURN OF AUTOMATIC DOCUMENTS TRANSFORMATION
    transform: null
  });

  obj.lastMessage = lastMessage;

  return obj;
};

You have also modify your Chat class schema to have lastMessage field.

Chat = Astronomy.Class({
  name: 'Chat',
  collection: Chats,
  fields: {
    title: {
      type: 'string'
    },
    // THE lastMessage FIELD HAS TO BE DEFINED IN THE SCHEMA
    lastMessage: {
      type: 'object'
    }
  }
});

Thanks to that, you will receive all the objects as you want. However when you call:

var chat = Chats.findOne();
console.log(chat); // Astronomy object.
console.log(chat.lastMessage); // Not Astronomy object!

You won't get Astronomy object calling chat.lastMessage it's because there are not relations defined. It's also on my TODO list because it's closely related to EJSONinification of Astronomy documents.

[banglashi]

Thanks a lot for the quick reply and the explanation, appreciate it. Keep up the good work and let me know if I can help with anything.

[lukejagodzinski]

No problem :). I'm glad that you and others are testing this package. Thanks to that I can move it forward to the point where it will be fully usable and fit almost all needs. If you want to help, please watch this and other Astronomy repositories so you will be notified about new issues. I will be adding new issues with discussion label, to talk about new features and how to implement them the way developers want it to be.

Regards :)