-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question on Updates #41
Comments
Natalya,
Unfortunately, I've changed jobs recently and I'm no longer working with C#
on a day-to-day basis. I'm happy to add you as an administrator to the
project, as you've had great contributions so far. I'd like to keep an eye
on things until I feel like things are well in control, but I don't see
myself able to contribute further to the project.
Does that sound okay to you?
Thanks!
Doug
…On Wed, Oct 2, 2019 at 4:34 PM Natalya Arbit ***@***.***> wrote:
Hello, Doug,
I understand things have been a bit busy lately. Is there any plans to
keep going with this library? There are couple of outstanding
PRs/questions. I'd also like to see underlying graphql-dotnet library
version get updated. It's on 3.0 pre-release with lots of bugs fixed some
of which are helpful outside of Dapper.GraphQL context. Anyways, thought
I'd just see where things were :) Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#41?email_source=notifications&email_token=AAHBOBQYLA5ABPYCDSEUYE3QMUOYXA5CNFSM4I44G3QKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HPIICEQ>,
or mute the thread
<https:/notifications/unsubscribe-auth/AAHBOBSTN3NSVMSKSLVASADQMUOYXANCNFSM4I44G3QA>
.
|
Sounds good, thank you, Doug! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, Doug,
I understand things have been a bit busy lately. Is there any plans to keep going with this library? There are couple of outstanding PRs/questions. I'd also like to see underlying graphql-dotnet library version get updated. It's on 3.0 pre-release with lots of bugs fixed some of which are helpful outside of Dapper.GraphQL context. Anyways, thought I'd just see where things were :) Thanks!
The text was updated successfully, but these errors were encountered: