rmosolgo / rmosolgo/graphql-ruby
Validate that interface field implementations match the abstract definition
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5.4k
- Forks
- 1.4k
- Avg merge
- 23h 19m
- Merged PRs (30d)
- 28
Description
GraphQL-Ruby will currently let you define
interface Thing {
name: String
}
type Object implements Thing {
name: Float
}
But this is not allowed by the spec. It should validate somewhere along the line to make sure that isn't possible.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the interface and object type validation path, using the example in the issue to trace where field implementations are checked. Add coverage for incompatible interface and object field types; done means the invalid schema is rejected according to the GraphQL specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100