shiftcode / dynamo-easy Goto Github PK

batch-get Request:

• add execNoMap function
• handle UnprocessedItems in response
• handle ProvisionedThroughputExceededException (needs further investigation)
• allow consistent read
• improve method to add keys forModel()

batch-get-single-table Request:

• handle UnprocessedItems in response
• handle ProvisionedThroughputExceededException (needs further investigation)
• allow consistent read

batch-write-single-table Request:

• handle ProvisionedThroughputExceededException (needs further investigation)

pagedRequest

• remove

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

investigate: if the put item model has a composite parition key we need to check for the sort key too

• update typings away from AttributeValue / AttributeMap to support better typing for custom mappers
• fix or remove excluded tests

either use partitionkey / sort key or hashkey / rangekey consistently (aws dynamodb uses hash / range for the two key types)

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

equivalent to BatchGetRequest

moment is currently a peerDependency but is only used as optional type with its Mapper.

there're many types not exported for public api

e.g. UpdateExpressionDefinitionFunction which would be pretty useful to work with

there are some issues with inheritance, investigate and document implications

support for inheritance (see form as an example), when using a DynamoStore of type Form it has some metadata from FrameOrderTemplate (SortKey), which leads to unexpected behavior

equivalent to TransactWriteRequest

• make a new 0.0.x release where we point to the new version of scoped package (just update the doc)
• merge the rxjs branch into master and create an introduction (coming from 0.0.x)
• merge initial version of greenkeeper

use definition function instead of actual condition

a getItem request requires all information about the primary key to be present (compared to query where the range key is optional)

• introduce a new request where we can define the options with the fluent api

Make sure we have all the required tooling setup to ensure good code quality.

git:pre-commit

• prettier
• tslint
• sort keys in package.json

git:push

• run tests

build

• generate and report coverage
• use code quality tool

periodically

• renovate (keep node dependencies up to date)
• security vulnerabilities

there are several TODO tasks with topic LOW:VALIDATION.
Research if validation is required or can be done trough typings. Think about concept on how to validate the input for expressions.

implement the size operator

operators and functions

work through all open FIXME & TODO tasks, and resolve or remove them

when accessing nested attribtues in expressions we need to be able to define the path not beeing keyof T otherwise the code will not compile. The restriction keyof T for attributeName only makes sence for top level attributes

for example:

https://www.npmjs.com/package/debug
or
https://www.npmjs.com/package/winston

implement generic paged loader to support paged data with any request which returns more than one item

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

somehow the IN exression does not work like expected i tried with L and S as attribute values, both calls were executed succesfully but no result was returned

On registry https://registry.npmjs.org/, the "latest" version (v0.1.0) of dependency @types/reflect-metadata has the following deprecation notice:

This is a stub types definition for reflect-metadata (https://github.com/rbuckton/ReflectDecorators). reflect-metadata provides its own type definitions, so you don't need @types/reflect-metadata installed!

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about @types/reflect-metadata's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

• EnumMapper (check again if required)
• check for unused code (DynamoErrorCode, DynamoError for example)

• node showcase project using glitch
• angular showcase project using stackblitz (also use pagedLoader to display data)

name conflicts are not resolved in ParamUtil.addExpression
(eg. when condition uses same property as update)

check if the provided values are valid for current action. check after mapping to an attribute value to be able to check for valid attribute value type

Check if size errors are handled on client side, or on server side

https://docs.aws.amazon.com/de_de/amazondynamodb/latest/APIReference/API_BatchGetItem.html

Make sure all the desired items are returned, handle UnprocessedKeys when payload is too large for single http request

provide an easy to use update api, something like

update expression

DynamoStore.update(primaryKey)
   .set(expr)
   .remove(expr)
   .add(expr)
   .delete(expr)
   .where(property('prop').eq('value'))

see doc

https://aws.amazon.com/blogs/aws/new-amazon-dynamodb-transactions/

always use wildcard import instead of named imports

a complex condition and(attribute().eq(), or(attribute().xx, attribute().yy)) expression seems to have wrong syntax (wrong parenthesis)

possibility to enable auto generation of timestamps like creationDate and lastUpdatedDate