Trevor Livingston

Results 11 issues of Trevor Livingston

I think it makes sense to potentially fork this project to maintainers willing to continue work on it and redirect users in the readme to the new maintained project. Afaik...

help wanted
question

**Describe the bug** pruneSchema will keep all implementations of an interface regardless of whether it is used or not. **To Reproduce** Steps to reproduce the behavior: Prune the following schema:...

🚨 **IMPORTANT: Please do not create a Pull Request without creating an issue first.** _Any change needs to be discussed before proceeding. Failure to do so may result in the...

This PR is to reproduce #5436 with a failing test.

### Issue workflow progress _Progress of the issue based on the [Contributor Workflow](https://github.com/the-guild-org/Stack/blob/master/CONTRIBUTING.md#a-typical-contributor-workflow)_ - [x] 1. The issue provides a reproduction available on Github, Stackblitz or CodeSandbox - [x] 2....

`processImport` : https://github.com/ardatan/graphql-tools/blob/master/packages/import/src/index.ts#L69 This function: 1. parses a document from a file, 2. iterates through each definition 3. prints the definition to a string 4. appends the string definition to...

Would be useful if it was possible to ignore missing types. These types might be present on a merge but missing from a specific import because they span different modules.

Node 8 has a breaking change in the way the error stack works. This change addresses that. Caveat: drops support for `depth`. Note: this is a breaking change!

This project is used but not maintained well. Let's add some volunteer maintainers to the project if you are too busy these days @subeeshcbabu ...