generateJava fails while .graphqlconfig is present in the schema dir
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 217
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
It seems the plugin simply concatenates all files inside the schema dir(s) and then tries to parse them. Why would it do so? Why does it include the .graphqlconfig file as well? There doesn't seem to be any option to exclude some files from the schema paths, unfortunatelly.
Execution failed for task ':app:generateJava'.
> Unable to parse the schema...
Invalid Syntax : offending token '"schemaPath"' at line 2 column 3
Then it prints the whole schema and apparently the contents of .graphqlconfig is part of it:
{
"schemaPath": "schema.graphql"
}
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 at the schema-directory handling used by the generateJava task and reproduce the failure with a .graphqlconfig file beside the schema. Trace how files are selected and parsed; done means generation no longer attempts to parse .graphqlconfig files, with coverage for this directory layout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100