Map Proxy API + Implementation

[mustafaiman]

fixes #18. Note that this API does not include executeOnKeys, addInterceptor and Predicates related methods. These will come with Serialization implementation.

[devOpsHazelcast]

Test PASSed.

[GhostInAMachine]

Why declare outside of the loop and then reassign within it?

[mustafaiman]

Putting it inside for method does not make its scope restricted to for loop. So I intentionally put them outside. This way it is less likely that someone mistakenly introduces the same variable later in the same method expecting it to be null. Matter of taste.

[GhostInAMachine]

If you use let variableName = value it will be restricted to the loop scope.

[mustafaiman]

Since we use Typescript compiler target as ES5 all lets are transpiled to var. So this would be worse. You expect it to be block scoped and get function scoped. Since Node 4 do not support majority of ES6 features we have to stick with ES5 and vars.

[GhostInAMachine]

OK

[mustafaiman]

There is requests from community to make Typescript support selectively turning on and off certain features: microsoft/TypeScript#4389 . I hope they support this feature and we can use cool ES6 features that Node already supports.

[devOpsHazelcast]

Test PASSed.

[jackspaniel]

Any idea when this will be published to npm?

[mustafaiman]

Hello @jackspaniel . This is already merged to master so it will be available with 0.3 release. 0.3 is planned to be released early June.