You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to query the subgraphMetadata and subgraphVersionMetadata I get the normal fields for searching a list of entities - first, where etc. Then when running the query I get an error that I didn't provide an id as though I were attempting to select from a singular entity.
This is likely because of the plural of metadata is probably also metadata. We've run into this with file data sources and went with "meta" which allows us to use "metas", but it may be something that can be solved in the schema dictionary.
{
subgraphMetadata(first: 10) {
id
}
}
The text was updated successfully, but these errors were encountered:
PR for this: #261
Given that this contains a breaking change, the release for this will take slightly more time, due to the change requiring a public announcement and a rollout procedure.
As part of the rollout procedure, it'll be live on staging for some time before it hits prod, so anyone interested in getting the fix early can use the staging subgraphs on hosted service for it.
As a recap, these are the staging subgraphs for mainnet and arbitrum one:
When attempting to query the
subgraphMetadata
andsubgraphVersionMetadata
I get the normal fields for searching a list of entities - first, where etc. Then when running the query I get an error that I didn't provide an id as though I were attempting to select from a singular entity.This is likely because of the plural of metadata is probably also metadata. We've run into this with file data sources and went with "meta" which allows us to use "metas", but it may be something that can be solved in the schema dictionary.
The text was updated successfully, but these errors were encountered: