-
Notifications
You must be signed in to change notification settings - Fork 172
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
feat: indexer v2 query migrations #3773
feat: indexer v2 query migrations #3773
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
id | ||
metadata | ||
} | ||
} | ||
} | ||
`; | ||
|
||
//NOT SUPPORTED ON THE CURRENT INDEXER |
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.
^ what's the best way to do this instead ?
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.
can we make use of the events_registry here?
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.
yes we can, good catch : )
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.
i will add it to expose it on the hasura api
@@ -604,13 +613,14 @@ export const getBlockNumberQuery = gql` | |||
} | |||
`; | |||
|
|||
//TODO: migrate code in which this query is called |
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.
Ack
@@ -136,6 +143,7 @@ export const getProjectAnchorByIdAndChainId = gql` | |||
* | |||
* @returns The project | |||
*/ | |||
//FIXME: Deprecated on indexer v2 ? |
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'd have to fetch all projects and do the filter on the frontend right ?
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.
On indexer v2 we don't consider allo-v1 projects. But i saw that the legacyProjects table is straight forward to implement, will do it.
9436e39
to
2724d6a
Compare
@@ -326,7 +329,7 @@ export const getApprovedApplication = gql` | |||
roundMetadata | |||
} | |||
metadata | |||
project: canonicalProject { | |||
project { |
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.
^ switch back to canonical
Update queries for Indexer V2 compatibility
Changes
Testing
Look Into