-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
[DO NOT MERGE] Compatibility for subgraph nft collections #4053
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Ignored Deployments
|
client, | ||
variables: { | ||
where: { | ||
...(dataSourceAddress ? { address: dataSourceAddress } : {}), | ||
...(dataSourceAddress |
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.
we now query by nft.collection.address
instead of nft.address
13e5465
to
da152fd
Compare
@@ -1,16 +1,16 @@ | |||
import Loading from 'components/Loading' | |||
import { Jb721DelegateTokensQuery } from 'generated/graphql' | |||
import { NfTsQuery } from 'generated/graphql' |
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.
Nit: capital T?
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.
ohh awk. looks like it's just the codegen output making NFTs -> NfTs query. just gonna leave it
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.
Thicc 🥇 sorry for such a delay. LGTM
Subgraph is still indexing, can be merged once complete. Plz approve in the meantime
Just a change to the graphql structure for querying JB721DelegateTokens—now simply called NFTs for simplicity. No functional changes
this will fail until the CI url is updated