-
Upstream `fast-deep-equal` can't handle `equal(new Set(["1", {}]), new Set(["1", {}]))` because it compares by reference `setA.has(setBElement)`.
Note that when running the correctness tests during…
-
### Is your feature request related to a problem?
I've been working with a schema file generated by Prisma.io but very early on found the issue that said generated uses field `equals` which causes co…
-
**Describe the bug**
Endless affinity list when using new schudlingPolicy field and a DATA_PLANE_AFFINITY in config
**To Reproduce**
Steps to reproduce the behavior:
1. Have a `DATA_PLANE_AFFINI…
-
**What is the current behavior?**
useDeepCompareEffect doesn't work while the deps is a map object;
**Steps to reproduce it and if possible a minimal demo of the problem. Your bug will get fixed m…
-
There are customers that use `DeepCollectionEquality().equals(a, b)` where `a` and `b` are e.g. `Map` (let's say json). It turns out this is **very slow**.
See https://github.com/zino-hofmann/graph…
-
The expo-router issue from #78 is fixed so we can now remove the patch for deep-equal package. if at the time of processing the fix is unreleased, find a way to test it out
-
对于那些不会扁平化依赖的包管理工具，比如pnpm，npm构建后不会包含上面两个依赖
-
```
⟩ npm list | grep chai
├─┬ chai@4.3.6
├─┬ chai-roughly-v2@2.0.11
```
```js
const chai = require('chai');
chai.use(require('chai-roughly-v2'));
const { expect } = chai;
expect(300.1).t…
-
## What is the Problem Being Solved?
We're now allowing nested data in errors. While async flow does not enforce that errors have the same message, we should enforce that any other nested data, at …
-
Definitely a nitpick but would love to see the README / benchmark logic updated to the LTS Node version!
https://nodejs.org/en/download
https://github.com/epoberezkin/fast-deep-equal/blob/master…