#7 Cacheable Object: Array/object updates should (non-deep) equality check before invalidating caches

Open
opened 3 years ago by towerofnix · 0 comments

I.e, each key in the original array/object should match (===) the new one, and vice versa (no added properties/items).

There are probably smarter ways to implement comparisons / update detection for non-primitives, so maybe that's worth investigating too. :P

I.e, each key in the original array/object should match (===) the new one, and vice versa (no added properties/items). There are probably smarter ways to implement comparisons / update detection for non-primitives, so maybe that's worth investigating too. :P
Sign in to join this conversation.
No Milestone
No assignee
1 Participants
Loading...
Cancel
Save
There is no content yet.