Skip to content

Conversation

@CH-EricLundberg
Copy link
Contributor

… explicit resolver, add option to prefer the resolver

…it resolver, add option to prefer the resolver
@CH-EricLundberg
Copy link
Contributor Author

Not sure if this is the best way to solve my issue but it seems to work. Happy to see if there are better places to put in this kind of check, I'm new to kotlin and this codebase.

@CH-EricLundberg
Copy link
Contributor Author

@oliemansm what do you think of this approach?

@CH-EricLundberg
Copy link
Contributor Author

@apottere (or anyone) is this project being maintained anymore? It feels very quiet. If it is I would love to get some feedback on the PR. :)

@oliemansm oliemansm merged commit a976939 into graphql-java-kickstart:master Sep 22, 2018
@oliemansm
Copy link
Member

@oliemansm
Copy link
Member

@CH-EricLundberg To answer your question regarding maintenance. I try to help out @apottere a bit wherever I can, but my main projects are claiming a lot of my time unfortunately. I'm not one of the original developers for any of the graphql-java projects either, so in a lot of cases it requires an effort similar to any of the other developers also depending on these projects (asking the questions or reporting the bugs). So any additional contributions fixing issues in any other form is appreciated. I'll try to take a look at and merge PRs more often, but currently still depending on Andrew for releasing new versions.

@CH-EricLundberg
Copy link
Contributor Author

Right on. And looks like there is a decent cadence on the release train, I'll keep my eye out for the next one so I can delete the local version. :)

@oliemansm oliemansm added this to the 5.3.1 milestone Sep 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants