profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/sensedeep/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

sensedeep/dynamodb-onetable 213

DynamoDB access and management for one table designs with NodeJS

sensedeep/onetable-cli 4

DynamoDB OneTable Migration CLI

sensedeep/onetable-migrate 4

DynamoDB OneTable Migrations Library

sensedeep/sensedeep 2

SenseDeep Serverless Monitoring and Troubleshooting for AWS

sensedeep/senselogs 1

Simple, flexible, dynamic, blazing fast logs designed for serverless.

sensedeep/dynamodb-metrics 0

DynamoDB Metrics for Single Table Designs

sensedeep/js-app 0

Javascript Client App

sensedeep/js-blend 0

Blend objects

sensedeep/js-clone 0

Clone objects and arrays

push eventsensedeep/onetable-migrate

Michael O'Brien

commit sha da3c94f61da52e71ef832f5dbd1d459254064957

DEV: bump version

view details

push time in an hour

push eventsensedeep/onetable-migrate

Michael O'Brien

commit sha af4acdb41dc273c0b2dfe75269603692cfd038d1

DOC: update readme.

view details

push time in an hour

release sensedeep/onetable-controller

v0.9.1

released time in 3 hours

created tagsensedeep/onetable-controller

tagv0.9.1

OneTable Migration Controller Sample

created time in 3 hours

delete tag sensedeep/onetable-controller

delete tag : v0.9.1

delete time in 3 hours

push eventsensedeep/onetable-controller

Michael O'Brien

commit sha 93e7ca3dbe73e6eaa46200316677077cc4586c90

DEV: update deps, add senselogs

view details

push time in 3 hours

release sensedeep/onetable-controller

v0.9.1

released time in 3 hours

created tagsensedeep/onetable-controller

tagv0.9.1

OneTable Migration Controller Sample

created time in 3 hours

release sensedeep/onetable-cli

v1.2.1

released time in 3 hours

created tagsensedeep/onetable-cli

tagv1.2.1

DynamoDB OneTable Migration CLI

created time in 3 hours

delete tag sensedeep/onetable-cli

delete tag : v1.2.1

delete time in 3 hours

push eventsensedeep/onetable-cli

Michael O'Brien

commit sha fe02ecc083d0c426d3ca8efc7a9c84f0a157e61a

DEV: build with udpated deps

view details

push time in 3 hours

release sensedeep/onetable-migrate

v1.1.2

released time in 3 hours

created tagsensedeep/onetable-migrate

tagv1.1.2

DynamoDB OneTable Migrations Library

created time in 3 hours

delete tag sensedeep/onetable-migrate

delete tag : v1.1.2

delete time in 3 hours

push eventsensedeep/onetable-migrate

Michael O'Brien

commit sha 3566ff54d77bc01f1441da6976dc07c9abe140eb

DEV: update for onetable 2.0

view details

push time in 3 hours

release sensedeep/onetable-migrate

v1.1.2

released time in 3 hours

created tagsensedeep/onetable-migrate

tagv1.1.2

DynamoDB OneTable Migrations Library

created time in 3 hours

delete tag sensedeep/onetable-migrate

delete tag : v1.1.2

delete time in 3 hours

push eventsensedeep/onetable-migrate

Michael O'Brien

commit sha 5d8075814e7a07124a561753e0a766a0dbcfe524

DEV: Support table-resident schema updates

view details

push time in 3 hours

release sensedeep/dynamodb-onetable

v2.0.0

released time in 4 hours

created tagsensedeep/dynamodb-onetable

tagv2.0.0

DynamoDB access and management for one table designs with NodeJS

created time in 4 hours

delete tag sensedeep/dynamodb-onetable

delete tag : v2.0.0

delete time in 4 hours

push eventsensedeep/dynamodb-onetable

Michael O'Brien

commit sha 89394792978acf60ce87e7f6956794915dde83c9

DOC: add schema spec

view details

push time in 4 hours

issue commentsensedeep/dynamodb-onetable

[BUG]: TypeError: model.transformReadItem is not a function

The fix is a little diffuse. Basically we refactored the schema code into ./Schema.js in recent releases. In doing this, Model.js referred to this.schema. However in some cases, this.schema as referring to a Schema class instance and in other cases it was referring to the actual schema JSON definition.

When creating a stand-alone model, it was using the JSON reference rather than the class reference. So the transform* methods were not present.

The fix required all models always using this.schema to refer to a Schema class instance and saving the JSON definition as this.schema.definition.

AndrewCathcart

comment created time in 6 hours

issue commentsensedeep/dynamodb-onetable

[BUG]: TypeError: model.transformReadItem is not a function

Ah that's great - I'll wait until you push it up to npm.

Would you mind pointing me towards the commit that fixed the issue / explain how the error was surfacing out of curiosity? Had a look through the commits but couldn't see anything obvious. Cheers.

AndrewCathcart

comment created time in 7 hours

issue commentsensedeep/dynamodb-onetable

[BUG]: TypeError: model.transformReadItem is not a function

We've committed the fix to the main branch 2.0.0 which is in pre-release.

Should be pushing the npm release in the next day or so.

AndrewCathcart

comment created time in 9 hours

issue commentsensedeep/dynamodb-onetable

[BUG]: TypeError: model.transformReadItem is not a function

Hello - any updates for this? Would be happy to work on this if you have any idea of a starting point.

AndrewCathcart

comment created time in 10 hours

startedsensedeep/dynamodb-onetable

started time in a day