包详细信息

mpath

aheckmann11.9mMIT0.9.0

{G,S}et object values using MongoDB-like path notation

mongodb, path, get, set

自述文件

mpath

{G,S}et javascript object values using MongoDB-like path notation.

Getting

var mpath = require('mpath');

var obj = {
    comments: [
      { title: 'funny' },
      { title: 'exciting!' }
    ]
}

mpath.get('comments.1.title', obj) // 'exciting!'

mpath.get supports array property notation as well.

var obj = {
    comments: [
      { title: 'funny' },
      { title: 'exciting!' }
    ]
}

mpath.get('comments.title', obj) // ['funny', 'exciting!']

Array property and indexing syntax, when used together, are very powerful.

var obj = {
  array: [
      { o: { array: [{x: {b: [4,6,8]}}, { y: 10} ] }}
    , { o: { array: [{x: {b: [1,2,3]}}, { x: {z: 10 }}, { x: 'Turkey Day' }] }}
    , { o: { array: [{x: {b: null }}, { x: { b: [null, 1]}}] }}
    , { o: { array: [{x: null }] }}
    , { o: { array: [{y: 3 }] }}
    , { o: { array: [3, 0, null] }}
    , { o: { name: 'ha' }}
  ];
}

var found = mpath.get('array.o.array.x.b.1', obj);

console.log(found); // prints..

    [ [6, undefined]
    , [2, undefined, undefined]
    , [null, 1]
    , [null]
    , [undefined]
    , [undefined, undefined, undefined]
    , undefined
    ]
Field selection rules:

The following rules are iteratively applied to each segment in the passed path. For example:

var path = 'one.two.14'; // path
'one' // segment 0
'two' // segment 1
14    // segment 2
  • 1) when value of the segment parent is not an array, return the value of parent.segment
  • 2) when value of the segment parent is an array
    • a) if the segment is an integer, replace the parent array with the value at parent[segment]
    • b) if not an integer, keep the array but replace each array item with the value returned from calling get(remainingSegments, item) or undefined if falsey.
Maps

mpath.get also accepts an optional map argument which receives each individual found value. The value returned from the map function will be used in the original found values place.

var obj = {
    comments: [
      { title: 'funny' },
      { title: 'exciting!' }
    ]
}

mpath.get('comments.title', obj, function (val) {
  return 'funny' == val
    ? 'amusing'
    : val;
});
// ['amusing', 'exciting!']

Setting

var obj = {
    comments: [
      { title: 'funny' },
      { title: 'exciting!' }
    ]
}

mpath.set('comments.1.title', 'hilarious', obj)
console.log(obj.comments[1].title) // 'hilarious'

mpath.set supports the same array property notation as mpath.get.

var obj = {
    comments: [
      { title: 'funny' },
      { title: 'exciting!' }
    ]
}

mpath.set('comments.title', ['hilarious', 'fruity'], obj);

console.log(obj); // prints..

  { comments: [
      { title: 'hilarious' },
      { title: 'fruity' }
  ]}

Array property and indexing syntax can be used together also when setting.

var obj = {
  array: [
      { o: { array: [{x: {b: [4,6,8]}}, { y: 10} ] }}
    , { o: { array: [{x: {b: [1,2,3]}}, { x: {z: 10 }}, { x: 'Turkey Day' }] }}
    , { o: { array: [{x: {b: null }}, { x: { b: [null, 1]}}] }}
    , { o: { array: [{x: null }] }}
    , { o: { array: [{y: 3 }] }}
    , { o: { array: [3, 0, null] }}
    , { o: { name: 'ha' }}
  ]
}

mpath.set('array.1.o', 'this was changed', obj);

console.log(require('util').inspect(obj, false, 1000)); // prints..

{
  array: [
      { o: { array: [{x: {b: [4,6,8]}}, { y: 10} ] }}
    , { o: 'this was changed' }
    , { o: { array: [{x: {b: null }}, { x: { b: [null, 1]}}] }}
    , { o: { array: [{x: null }] }}
    , { o: { array: [{y: 3 }] }}
    , { o: { array: [3, 0, null] }}
    , { o: { name: 'ha' }}
  ];
}

mpath.set('array.o.array.x', 'this was changed too', obj);

console.log(require('util').inspect(obj, false, 1000)); // prints..

{
  array: [
      { o: { array: [{x: 'this was changed too'}, { y: 10, x: 'this was changed too'} ] }}
    , { o: 'this was changed' }
    , { o: { array: [{x: 'this was changed too'}, { x: 'this was changed too'}] }}
    , { o: { array: [{x: 'this was changed too'}] }}
    , { o: { array: [{x: 'this was changed too', y: 3 }] }}
    , { o: { array: [3, 0, null] }}
    , { o: { name: 'ha' }}
  ];
}

Setting arrays

By default, setting a property within an array to another array results in each element of the new array being set to the item in the destination array at the matching index. An example is helpful.

var obj = {
    comments: [
      { title: 'funny' },
      { title: 'exciting!' }
    ]
}

mpath.set('comments.title', ['hilarious', 'fruity'], obj);

console.log(obj); // prints..

  { comments: [
      { title: 'hilarious' },
      { title: 'fruity' }
  ]}

If we do not desire this destructuring-like assignment behavior we may instead specify the $ operator in the path being set to force the array to be copied directly.

var obj = {
    comments: [
      { title: 'funny' },
      { title: 'exciting!' }
    ]
}

mpath.set('comments.$.title', ['hilarious', 'fruity'], obj);

console.log(obj); // prints..

  { comments: [
      { title: ['hilarious', 'fruity'] },
      { title: ['hilarious', 'fruity'] }
  ]}

Field assignment rules

The rules utilized mirror those used on mpath.get, meaning we can take values returned from mpath.get, update them, and reassign them using mpath.set. Note that setting nested arrays of arrays can get unweildy quickly. Check out the tests for more extreme examples.

Maps

mpath.set also accepts an optional map argument which receives each individual value being set. The value returned from the map function will be used in the original values place.

var obj = {
    comments: [
      { title: 'funny' },
      { title: 'exciting!' }
    ]
}

mpath.set('comments.title', ['hilarious', 'fruity'], obj, function (val) {
  return val.length;
});

console.log(obj); // prints..

  { comments: [
      { title: 9 },
      { title: 6 }
  ]}

Custom object types

Sometimes you may want to enact the same functionality on custom object types that store all their real data internally, say for an ODM type object. No fear, mpath has you covered. Simply pass the name of the property being used to store the internal data and it will be traversed instead:

var mpath = require('mpath');

var obj = {
    comments: [
      { title: 'exciting!', _doc: { title: 'great!' }}
    ]
}

mpath.get('comments.0.title', obj, '_doc')            // 'great!'
mpath.set('comments.0.title', 'nov 3rd', obj, '_doc')
mpath.get('comments.0.title', obj, '_doc')            // 'nov 3rd'
mpath.get('comments.0.title', obj)                    // 'exciting'

When used with a map, the map argument comes last.

mpath.get(path, obj, '_doc', map);
mpath.set(path, val, obj, '_doc', map);

LICENSE

更新日志

0.9.0 / 2022-04-17

  • feat: export stringToParts()

0.8.4 / 2021-09-01

  • fix: throw error if parts contains an element that isn't a string or number #13

0.8.3 / 2020-12-30

  • fix: use var instead of let/const for Node.js 4.x support

0.8.2 / 2020-12-30

  • fix(stringToParts): fall back to legacy treatment for square brackets if square brackets contents aren't a number Automattic/mongoose#9640
  • chore: add eslint

0.8.1 / 2020-12-10

  • fix(stringToParts): handle empty string and trailing dot the same way that split() does for backwards compat

0.8.0 / 2020-11-14

  • feat: support square bracket indexing for get(), set(), has(), and unset()

0.7.0 / 2020-03-24

0.6.0 / 2019-05-01

  • feat: support setting dotted paths within nested arrays

0.5.2 / 2019-04-25

  • fix: avoid using subclassed array constructor when doing map()

0.5.1 / 2018-08-30

  • fix: prevent writing to constructor and prototype as well as proto

0.5.0 / 2018-08-30

  • BREAKING CHANGE: disallow setting/unsetting proto properties
  • feat: re-add support for Node < 4 for this release

0.4.1 / 2018-04-08

  • fix: allow opting out of weird $ set behavior re: Automattic/mongoose#6273

0.4.0 / 2018-03-27

  • feat: add support for ES6 maps
  • BREAKING CHANGE: drop support for Node < 4

0.3.0 / 2017-06-05

  • feat: add has() and unset() functions

0.2.1 / 2013-03-22

  • test; added for #5
  • fix typo that breaks set #5 Contra

0.2.0 / 2013-03-15

  • added; adapter support for set
  • added; adapter support for get
  • add basic benchmarks
  • add support for using module as a component #2 Contra

0.1.1 / 2012-12-21

  • added; map support

0.1.0 / 2012-12-13

  • added; set('array.property', val, object) support
  • added; get('array.property', object) support

0.0.1 / 2012-11-03

  • initial release