gives and needs sugar about depject HOT 7 CLOSED

published this as a helper module: depnest! 🎉

from depject.

apart from 1, I think these complicate the code too much. better to be simple. it's a few more characters... but lots more logic & tests. I don't think it's worth it, and the discussion is a bikeshed!

but I don't mind if you have a library function that can export a correct depject object, but use whatever syntax you like.

from depject.

Just handling the first case would be fine with me.

from depject.

Oh, actually, I know how I'd put it: this proposal is like an electric can opener, an electric can opener seems like a convienence, because it takes slightly less time to open a can. But, it's a lot more expensive, and how much time do you spend opening cans per day? Also, it's too large to fit in the drawer, so it must live on the bench, there are a lot more ways for it to break down, and it requires a power socket, that could otherwise have been used for something more useful (like blender - which enables you to do something you can't otherwise do).

Electric Can Openers seem like a convience, but they don't really make your life simpler. Persue simplicity, not convienence. Simplicity saves time in the long run, when it matters, when you need to read the code to understand how it really works. When the power goes out. When you have to debug something.

from depject.

exports.create = function(api) {
  return sugar({
     'cats.actions': { create, destroy }
  })
}

yet another way to open the can (by @mixmix + matt)

from depject.

from depject.

this seems resolved, closing

from depject.