Does not work with Object.values/Object.keys

import memoizeState from "memoize-state";

const selector = memoizeState(s => {
  return Object.values(s.items).map(x => x.text);
});

const state = {
  items: {
    1: { text: "foo" }
  }
};

console.log(selector(state));
// expected ['foo']
// actual   ['foo']  ✅

const newState = {
  ...state,
  items: {
    ...state.items,
    2: { text: "bar" }
  }
};

console.log(selector(newState));
// expected ['foo', 'bar']
// actual   ['foo'] 🚩

Codesandbox demo

[theKashey]

The fix was added into the underlying proxyequal, but not yet released.

[theKashey]

That’s actually a good issue. You are assessing deeply nested text property, and algorithm thinks that it’s what you are interested in - not item, but only item.text. By the same long - not items but item. Result is clear - new stuff is ignored.

It’s working for arrays, as long length property changes, but not for objects. The funny moment - it’s impossible to solve this problem with the current algorithm.

Idea - for every enumeration operation(ownKeys proxy hook) “asses” a secret property = concatenated keys, but this is not a quite ES5 polyfill compatible. I really don’t want to use old spread_guard logic.

@dai-shi - might be you have some bright ideas?