hasura / hasura/graphql-engine
Incorrect instruction and cli for connecting to subgraph given there are multiple subgraphs
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
Issue can be replicated when there are multiple subgraphs.
Initialising connector to a subgraph named: agblog_subgraph. Instead of providing **subgraph name** in cli we need to **define the path** of subgraph.yaml for respective subgraph.
Example
ddn connector init agblog_mysql --subgraph `agblog_subgraph/subgraph.yaml` --hub-connector hasura/mysql
This [doc](https://hasura.io/connectors/mysql) suggests just the name.
`ddn connector init my_mysql --subgraph my_subgraph --hub-connector hasura/MySQL
`
Here is the error when just the subgraph name is mentioned as per the instruction
Contributor guide
Research direction
Start with the linked MySQL connector documentation and the `ddn connector init` CLI entry point. Compare the documented subgraph argument with behavior when multiple subgraphs exist; done when the CLI and instructions consistently accept or describe the correct subgraph reference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql
- Domain
- cli, documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100