Collections in grouper object about meteor-admin HOT 4 CLOSED

Thanks for your first PR. I will implement this tomorrow.

Out of interest, what's the benefit of grouping your collections?

from meteor-admin.

It keeps the window object less cluttered on the client, but I only do it in really large apps, and it's not really critical. It's also useful when you're creating the collection in a package and you want to attach everything to a single exported variable. Similar to how Meteor.users is attached to Meteor instead of just Users. You handle the users collection specially, but another package could export in the same way.

from meteor-admin.

@aldeed Could you share the snippet or method you use for parsing strings with '.' to return JS objects?

from meteor-admin.

function lookup(obj) {
    var ref = window;
    var arr;
    if (typeof obj === "string") {
      arr = obj.split(".");
      while(arr.length && (ref = ref[arr.shift()]));
      if (!ref) {
        throw new Error(obj + " is not in the window scope");
      }
      return ref;
    }
    return obj;
  }

That takes either the object itself or a string representation of it with dots. If it's an object, just returns it, otherwise lookup based on the string pieces. It's client-specific, though, so if used in server code, you'd have to detect whether client or server, and change that first line to ref = global (I think) on the server.

from meteor-admin.