digitalplaywright

//file app/serializers/application.js

import DS from "ember-data";
import Ember from "ember";

export default DS.ActiveModelSerializer.extend({

  serializeHasMany: function (record, json, relationship) {
    var key = relationship.key;
    var hasManyRecords = Ember.get(record, key);

digitalplaywright

var Post = DS.Model.extend({
  title:      DS.attr('string'),  
  details:    DS.attr('string'),
  user: DS.belongsTo('user')
});

export default Post;

digitalplaywright

Handlebars.registerHelper("ifData", function(property, fn)
{
  var context = (fn.contexts && fn.contexts[0]) || this;
  var args    = [property];

  var canAction = function(can_args)
  {
    alert('I was called for '+can_args[0].get('id'));
    return true;
  };

digitalplaywright

Handlebars.registerHelper("can", function(actor, action, object, fn)
{
  var context = (fn.contexts && fn.contexts[0]) || this;


  var canAction = function(can_args)
  {
    var rules = context.container.lookup('rules:eval');

    return rules.can({activity: can_args[1], actor: can_args[0], object: can_args[2] });

digitalplaywright

Handlebars.registerHelper('can', function(permissionName, options){

  var rules = this.container.lookup('rules:eval');

  if ( options == null ){
    options = { activity: permissionName };
  }else{
    options['activity'] = permissionName;
  }

digitalplaywright

.DS_Store
node.json
tmp/

digitalplaywright

We use inverse_of in three ways in Mongoid. I've attempted to translate the way we currently use inverse_of in Mongoid to the @bkeepers inverse_of syntax:

2. Update: use :class_name to specify the class and :inverse_of to specify the inverse association if the :class_name and :inverse_of association can not be inferred from the association definition.

To declare multiple associations to the same model.

I believe :inverse_of and :class_name can be inferred in the trivial case where the field name equals the class or collection name.

digitalplaywright

1. To declare multiple fields using the same embedded model, like e.g:

class Profile
  include Mongoid::Document

  embeds_many :i_am_a,    :class_name => "TagInteraction", :inverse_of => :i_am_a
  embeds_many :i_love_to, :class_name => "TagInteraction", :inverse_of => :i_love_to
end

digitalplaywright

We use inverse_of in three ways in Mongoid. I've attempted to translate the way we currently use inverse_of in Mongoid to the @bkeepers inverse_of syntax:

2. Update: use :class_name to specify the class and :inverse_of to specify the inverse association if the :class_name and :inverse_of association can not be inferred from the association definition.

To declare multiple associations to the same model.

I believe :inverse_of and :class_name can be inferred in the trivial case where the field name equals the class or collection name.