feat: validate graphql schema at build time

[saihaj]

we want to run GraphQL Schema validations at the build time to crash early

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Pages

Latest commit:	7439f34
Status:	✅  Deploy successful!
Preview URL:	https://3ee20ec5.graph-tooling.pages.dev
Branch Preview URL:	https://saihaj-1364.graph-tooling.pages.dev

View logs

[changeset-bot]

🦋 Changeset detected

Latest commit: 7439f34

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@graphprotocol/graph-cli	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package	Version	Info
@graphprotocol/graph-cli	0.64.0-alpha-20231213180901-055b47e	npm ↗︎ unpkg ↗︎

[YaroShkvorets]

@saihaj any reason this was abandoned as draft?

[saihaj]

@saihaj any reason this was abandoned as draft?

Hey @YaroShkvorets so if you see the META_SCHEMA_GRAPH_NODE there were some fix needed for schema in graph-node I don't think my PR ever got merged. Also this required some more testing.

We also need a reliably way to pin to a graph-node version that a user will deploy to. There can be features from graph-node that user is trying to use in the subgraph but are not available in a release. So the approach of pinning to master on GitHub won't work. I think better would be looking at manifests and then creating URL for META_SCHEMA_GRAPH_NODE.

So that is one reason it was stranded. Then we also had bunch of discussions and exploration of solving this issue via the NAPI (or similar tool) initiative. Where graph-node would publish a common crate that can be used within CLI so we use same function graph-node uses and provide much more detailed error info.

reflecting back I think better the former approach (the one this PR takes) is probably the best. Then in future figure out NAPI (we have PR that should be able to land after some extensive testing)