Improve transactions support

[gaperton]

Design clean and concise transactions mechanic.

• collection.each must be transactional by default
• obj.transaction must pass an object as an argument to inner function.
• no change:attr bubbling for collections. Forbid this shit. Design something better, for example:
  • beforeChanges event, happening instead.
• add attribute-level subscription for сhanges and object-level event maps
• add transaction traces to collection: changed, added, removed attrs.
• collection.set must take transaction object: { add, change, remove }
• model and collection must have the method for retrieving the last transaction. Transaction object must contain serialized JSON data, suitable for network transfer and set.
• implement deep objects comparison, generating transaction.

Think about all this stuff as a whole, it becomes messy, something needs to be done. Fuck backward compatibility.

[gaperton]

Found good solution and working on it. Transactions core (Record/Collection) will be separated from the rest of the stuff, written with ES6 from the ground, and I will put it in separate package.

NestedTypes will use it and add proxied lodash functions, events, REST, etc.

In this way, code will become actually hackable by other people. All issues with ES6 support, ownership, and transactions will be solved. Speed of fetching large collections with deeply nested structures should dramatically improve. In fact, I believe it will be the fastest JS serialization engine in the world.

Also, this phase will open the path to TypeScript integration, which is, I believe, is the next big thing in JS world.

[gaperton]

Fixed in develop.