Skip to content
This repository was archived by the owner on Jan 3, 2022. It is now read-only.

feat: add filterResponse deep compare with fast-deep-equal - #119

Closed
shanejonas wants to merge 1 commit into
MetaMask:masterfrom
xops:feat/filter-reponse-deep-compare
Closed

shanejonas wants to merge 1 commit into
MetaMask:masterfrom
xops:feat/filter-reponse-deep-compare

Conversation

@shanejonas

Copy link
Copy Markdown
Contributor

No description provided.

@shanejonas
shanejonas requested a review from a team as a code owner September 28, 2020 18:09
@shanejonas
shanejonas force-pushed the feat/filter-reponse-deep-compare branch 3 times, most recently from 1b1d108 to 95852cc Compare September 28, 2020 18:11
@shanejonas shanejonas changed the title feat: add filterResponse deep compare with fast-deep-compare feat: add filterResponse deep compare with fast-deep-equal Sep 28, 2020
@shanejonas
shanejonas force-pushed the feat/filter-reponse-deep-compare branch 2 times, most recently from 80a8d17 to 2a3ce4a Compare September 28, 2020 18:16
@shanejonas
shanejonas force-pushed the feat/filter-reponse-deep-compare branch from 2a3ce4a to 13e1ef7 Compare September 29, 2020 16:15
@Gudahtt

Gudahtt commented Oct 6, 2020

Copy link
Copy Markdown
Member

@shanejonas Could you explain what this change is, and why it's being made?

@shanejonas

Copy link
Copy Markdown
Contributor Author

Sure, this change extends the current filterResponse to support not just shallow arrays of strings, but deep compare of objects as well.

@rekmarks rekmarks closed this Dec 16, 2020
@rekmarks
rekmarks deleted the branch MetaMask:master December 16, 2020 16:34
@shanejonas

Copy link
Copy Markdown
Contributor Author

@rekmarks any reason why this was closed? continuing to support shallow strings only for filters doesn't sound like a long term solution?

@rekmarks

Copy link
Copy Markdown
Contributor

Shoot, I just renamed the default branch and deleted master, forgetting that doing so closes open PRs 🤦‍♂️. Can you please reopen the PR against main? Sorry!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants