Objective
Improve the subgraph integration in dAppBooster to support flexible URL construction, shared queries across subgraphs, schema-driven query authoring, and better documentation for parameterized queries.
Rationale
The current subgraph setup has friction points that force repetitive work (duplicating queries per subgraph), require manual URL assembly with three separate env vars, and lack schema support for query authoring. Addressing these reduces boilerplate, prevents errors, and lowers the barrier for new contributors working with subgraphs.
Scope
In scope:
- Development URL construction with
user-id, subgraph-slug, and subgraph-version parameters (expected format: https://api.studio.thegraph.com/query/[user-id]/[subgraph-slug]/version/[subgraph-version])
- Mechanism to define a query once and run it against multiple subgraphs without duplicating it into each subgraph folder
- Schema-first workflow so queries can be written against a pre-generated schema
- Documentation section covering parameterized queries
Out of scope:
- Production/decentralized network URL changes
- Migration to alternative subgraph providers
Architecture & technical considerations
No response
Dependencies
No response
Issue breakdown
Acceptance criteria
Owner / DRI
No response
Target milestone
No response
Objective
Improve the subgraph integration in dAppBooster to support flexible URL construction, shared queries across subgraphs, schema-driven query authoring, and better documentation for parameterized queries.
Rationale
The current subgraph setup has friction points that force repetitive work (duplicating queries per subgraph), require manual URL assembly with three separate env vars, and lack schema support for query authoring. Addressing these reduces boilerplate, prevents errors, and lowers the barrier for new contributors working with subgraphs.
Scope
In scope:
user-id,subgraph-slug, andsubgraph-versionparameters (expected format:https://api.studio.thegraph.com/query/[user-id]/[subgraph-slug]/version/[subgraph-version])Out of scope:
Architecture & technical considerations
No response
Dependencies
No response
Issue breakdown
user-id,subgraph-slug, andsubgraph-versionAcceptance criteria
Owner / DRI
No response
Target milestone
No response