Saturday, May 12, 2018

another reminder that JavaScript is not C#

When you hydrate an object from an Observable in an Angular application, do not expect values landing at the set half of a TypeScript getsetter to run the setter logic and hydrate a private field while perhaps doing something else and something more. Instead you are merely monkey patching over the getsetter with a new field and destroying any robust functionality for the get that might be to boot too. The constructor at your TypeScript class ain't gonna go off neither, I reckon. We're kinda slummin' it, huh?

No comments:

Post a Comment