Then maybe you have two options:
option 1. move that to the controller or the blueprint, or even a policy (depending on your case). You can keep the attr function if it has some use elsewhere.

//api/controllers/EventController.js
module.exports = {
  findOne: function( req, res ) {
    var eventId;// = bla bla.. get it from req or from wherever you're getting it!
    Event.findOne(eventId).exec(function(err, eve){
      if ( err ) return res.serverError( err );
      if ( !eve ) return res.notFound( 'No event found with ID ' + eventId );

      var eveObj = eve.toObject();
      //temp workaround for https://github.com/balderdashy/waterline/issues/891#issuecomment-88361748
      eveObj.toJSON = undefined;
      eveObj.hasExpired = eve.hasExpired();//assuming you've implemented hasExpired as an attr func

      res.ok(eveObj);//bye bye darling
    });
  }
};

option 2. override toJSON in your model to add all that fancy stuff. This is a good option if you always want to add that attr to the json of your event. You can find an example of overriding toJSON in this comment https://github.com/balderdashy/waterline/issues/317#issuecomment-38376374

Good luck!

[Feature Request] callback afterFind #5471

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions