nicklozon / meteor-collection-revisions Goto Github PK

When I save a document, I have my first version of my document - the initial version. No revisions-property has been created on the document so far, right? Now I change something, save it and get my second version. Now the revisions-property is set to an array having one document, namely the document in it's first version.

If I now try to revert my document to the first version, my changes, done in my second version, are gone. I would like to have them now stored as a new document in the revisions array - that said - now being in the 3rd version ...

The new release of Meteor v1.6.1 now requires your code to use coffeescript in version 2.x. which means that every project would have to update it's dependency for the coffeescript package.

I've never written coffeescript myself. What I could help with is rewriting the code in plain ES6 javascript, if you would be happy with it...

For now I just tried to copy the code into a coffeescript 2 online compiler which didn't throw any errors, so I guess it should all work as expected.