-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: downstream referential equality errors #144
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,7 +7,7 @@ import { Connector, Provider as Eip1193Provider, Web3ReactStore } from '@web3-re | |
import { WalletConnect } from '@web3-react/walletconnect' | ||
import { SupportedChainId } from 'constants/chains' | ||
import { atom, useAtom } from 'jotai' | ||
import { PropsWithChildren, useEffect, useMemo } from 'react' | ||
import { PropsWithChildren, useEffect, useMemo, useRef } from 'react' | ||
import JsonRpcConnector from 'utils/JsonRpcConnector' | ||
|
||
export type Web3Connection = [Connector, Web3ReactHooks] | ||
|
@@ -104,12 +104,30 @@ export function ActiveWeb3Provider({ | |
[jsonRpcUrlMap, defaultChainId] | ||
) | ||
|
||
connections = [metaMaskConnection, walletConnectConnectionQR, walletConnectConnectionPopup, networkConnection] | ||
if (integratorConnection) connections = [integratorConnection, ...connections] | ||
const key = useRef(0) | ||
connections = useMemo(() => { | ||
// while react warns against triggering side effects in useMemo, | ||
// in this instance we're only using the mutated value to generate a key, | ||
// so tightly coupling the key update with the memo update shouldn't cause any issues, | ||
// and most clearly expresses the intent | ||
key.current += 1 | ||
NoahZinsmeister marked this conversation as resolved.
Show resolved
Hide resolved
|
||
return [ | ||
integratorConnection, | ||
metaMaskConnection, | ||
walletConnectConnectionQR, | ||
walletConnectConnectionPopup, | ||
networkConnection, | ||
].filter((connection): connection is Web3Connection => Boolean(connection)) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit: I think you can add the type to the template parameters and just use Boolean, so that the actual code remains simpler. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. hm i tried this and i don't think it's possible - similar issue (without a fix) described here: microsoft/TypeScript#16069 |
||
}, [ | ||
integratorConnection, | ||
metaMaskConnection, | ||
walletConnectConnectionQR, | ||
walletConnectConnectionPopup, | ||
networkConnection, | ||
]) | ||
|
||
const key = `${connections.length}+${Object.entries(jsonRpcUrlMap)}+${propsDefaultChainId}+${defaultChainId}` | ||
return ( | ||
<Web3ReactProvider connectors={connections} key={key}> | ||
<Web3ReactProvider connectors={connections} key={key.current}> | ||
{children} | ||
</Web3ReactProvider> | ||
) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
connections
is potentially invalid if it changes over time. Does this export need to be reconsidered?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so, while i'm still not thrilled about this export, i checked and all the other components that use
connections
are children ofWeb3ReactProvider
, and since the whole point of this pr is ensuring that this component re-renders wheneverconnections
changes, there shouldn't be any immediate issuesmy vote would be to merge this and consider a refactor in a later pr? can make an issue if there's agreement
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is the case, could there just be a hook to expose connections within the React lifecycle? I'm fine with doing this as a follow up, but it seems brittle and not future-proof, so I may just do it today.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tracking in #145