Why are we extending Mongo collection, what's that for?

[tomRedox]

I copied that code from the MDG examples, but what is the reason for doing it? Remove it if it's not doing anything.

Abhi's comment: "I don't think you should extend Mongo.Collection. You gain nothing. And may confuse people who don't know what his new collection generator is."

[serkandurusoy]

They just use that as a development pattern to organize important data mutation methods under the collection's namespace.

It may be desirable for large applications or for developers who are used to rails/java/.net style programming with orm's.

In fact, I'd highly suggest you take a look at astronomy for your model layer. I think astronomy is better suited towards line of business apps.

[tomRedox]

Thanks @serkandurusoy, I will definitely look at astronomy, it's on the list. I wanted to have done the work 'long-hand' first to really understand what's going on under the hood before moving onto an abstraction. I'm a .net programmer by day, so I'm completely used to working with an ORM abstraction.

[serkandurusoy]

Cool! Line of business apps is kind of "my thing" and I am still developing them on Blaze and wanting to move on to React, so this repo is very valuable to me. So let me know if there's anything I can do to help.

[tomRedox]

Great stuff, will do

[AnnotatedJS]

I ditto serkandurusoy's previous comment. I have my meteor-react-start-app and was also 'back-stage' working on extending it with 'line of business' features and specifically a solution for a more-or-less normalized many-to-many relationship, in my case User --Membership--Group.

See also my GreatAlbums app for my previous blaze implementation of Line Of Business features.

[tomRedox]

@AnnotatedJS: Thanks René, much appreciated.