Sign Up for Free

RunKit +

Try any Node.js package right in your browser

This is a playground to test code. It runs a full Node.js environment and already has all of npm’s 1,000,000+ packages pre-installed, including dynamodb-get-expression-attributes with all npm packages installed. Try it out:

var dynamodbGetExpressionAttributes = require("dynamodb-get-expression-attributes")

This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.

dynamodb-get-expression-attributes v2.1.1

A simple utility to extract the needed `ExpressionAttributeNames` and `ExpressionAttributeValues` from a DynamoDB query/scan expression.

dynamodb-get-expression-attributes

A simple utility to extract the needed ExpressionAttributeNames and ExpressionAttributeValues from a DynamoDB KeyConditionExpression, FilterExpression and/or ProjectionExpression query/scan expression.

Instead of this:

const params = {
  TableName: 'sessions',
  FilterExpression: '#user = :user and #date between :start and :end',
  ProjectionExpression: '#date, #user, #session',
  ExpressionAttributeNames: {
    '#user': 'user',
    '#date': 'date',
    '#session': 'session'
  },
  ExpressionAttributeValues: {
    ':user': '123456',
    ':start': '2017-02-01',
    ':end': '2017-03-01'
  }
};

You can do this:

const getExpressionAttributes = require('dynamodb-get-expression-attributes');

const params = getExpressionAttributes({
  TableName: 'sessions',
  FilterExpression: '#user = :user and #date between :start and :end',
  ProjectionExpression: '#date, #user, #session'
}, { user:'123456', start:'2017-02-01', end:'2017-03-01' });

Install

$ npm install --save dynamodb-get-expression-attributes

Test

$ npm test

Limitations

  • The attribute name placeholders are assumed to be the same as the keys in your database. A KeyConditionExpression like #yr = :yyyy won't work. This can be fixed by providing an ExpressionAttributeNames attribute.
  • Only attribute names and values included in the "data" object are used. Defining a placeholder in only an expression but not "data" will not work.

Changelog

  • v2.1.0: Doesn't clobber the existing ExpressionAttributeNames and ExpressionAttributeValues attributes.
  • v2.0.0: Creates ExpressionAttributeNames and ExpressionAttributeValues using a provided KeyConditionExpression, FilterExpression and/or ProjectionExpression and a "data" object.
  • v1.0.0: Creates ExpressionAttributeNames and ExpressionAttributeValues from a provided "data" object.

License

(The MIT License)

Copyright (c) 2017 John Flesch.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

RunKit is a free, in-browser JavaScript dev environment for prototyping Node.js code, with every npm package installed. Sign up to share your code.
Sign Up for Free