Is there anyone willing to help me get started with GraphQLD.

I have some experience with graphql in node.

My D is intermediate at best but i can learn fast with guidance.

I am able to build and deploy vibe-d apps locally and on heroku.

Basically, I'm looking for someone to stand-in in lieu of the documentation (currently WIP) to help me connect a basic vibe-d app to a graphql backend.

I am willing to contribute to documentation (and produce premium quality video tutorials) once i am proficient using the package.

Thanks in advance.

On Tuesday, 15 December 2020 at 16:25:29 UTC, Trustee wrote:
> Is there anyone willing to help me get started with GraphQLD.
>
> I have some experience with graphql in node.
>
> My D is intermediate at best but i can learn fast with guidance.
>
> I am able to build and deploy vibe-d apps locally and on heroku.
>
> Basically, I'm looking for someone to stand-in in lieu of the documentation (currently WIP) to help me connect a basic vibe-d app to a graphql backend.
>
> I am willing to contribute to documentation (and produce premium quality video tutorials) once i am proficient using the package.
>
> Thanks in advance.

I had wanted to do a written tutorial with it but since it isn't well documented, I've postpone it until I figure it out. It'll take a while to learn the API from code...and I kind of moved onto something else. (and I've raised this issue with D packages in a post I wrote)


It's quite unfortunately that folks spend months developing something but then don't invest few hrs to make it easy for others to use and contribute back.

I'm pretty sure they use it at Symmetry Investments though.

On Wednesday, 16 December 2020 at 08:33:09 UTC, aberba wrote:
> On Tuesday, 15 December 2020 at 16:25:29 UTC, Trustee wrote:
>> Is there anyone willing to help me get started with GraphQLD.
>>
>> I have some experience with graphql in node.
>>
>> My D is intermediate at best but i can learn fast with guidance.
>>
>> I am able to build and deploy vibe-d apps locally and on heroku.
>>
>> Basically, I'm looking for someone to stand-in in lieu of the documentation (currently WIP) to help me connect a basic vibe-d app to a graphql backend.
>>
>> I am willing to contribute to documentation (and produce premium quality video tutorials) once i am proficient using the package.
>>
>> Thanks in advance.
>
> I had wanted to do a written tutorial with it but since it isn't well documented, I've postpone it until I figure it out. It'll take a while to learn the API from code...and I kind of moved onto something else. (and I've raised this issue with D packages in a post I wrote)
>
>
> It's quite unfortunately that folks spend months developing something but then don't invest few hrs to make it easy for others to use and contribute back.
>
> I'm pretty sure they use it at Symmetry Investments though.

Hmmm... Maybe the universe is trying to tell us something...

Looks like one or both of us are meant to figure it out.

According to what you've said, you're still in a state of postponement, while I, on the other hand have just returned from my SECOND postponement. :(

I even considered falling back to Node and Prisma but I just can't bring myself to do it. Not now that I know D. It's just not something I could stomach. I have tried.

Guess I'm just gonna have to suck it up. Brush up on the intricacies of D, and dig into the codebase. It would seem to be the path of least resistance. I'll come out the other side a better person for it, no doubt.

With the number of key D packages that happen to be attributed to Symmetry Investments/Kaleidic Associates, I wouldn't want to trouble them with this directly at this juncture. Especially as I haven't even given it a proper go yet.

From the outside looking in, they have gone above and beyond already. If they say it's a WIP, I'm good with that. It's all a generous contribution. And they seem to have a strong track record of making those.

I, on the other hand, can use this as an opportunity to make my first.

Seems like a little less of a trudge now I guess

On Tuesday, 15 December 2020 at 16:25:29 UTC, Trustee wrote:
>
>connect a basic vibe-d app to a graphql backend.
>

umm, what?
Did you mean write graphql backend using vibe.d?

On Thursday, 17 December 2020 at 14:49:42 UTC, evilrat wrote:
> On Tuesday, 15 December 2020 at 16:25:29 UTC, Trustee wrote:
>>
>>connect a basic vibe-d app to a graphql backend.
>>
>
> umm, what?
> Did you mean write graphql backend using vibe.d?

Yes. But more so, I want to learn the ins and outs of the graphqld package. What's contained, what isn't (in terms of what functionality available and/or possible - e.g. client gen???, xSQL gen), what to build to add to complement/contribute to the package. First phase, docs.

I have already begun working through the code and it's beginning to make sense.

To be fair it's more about my fluency in D than the package itself. I haven't been coding for a while so it gets kinda rusty.

Any help would be appreciated though.

On Thursday, 17 December 2020 at 14:49:42 UTC, evilrat wrote:
> On Tuesday, 15 December 2020 at 16:25:29 UTC, Trustee wrote:
>>
>>connect a basic vibe-d app to a graphql backend.
>>
>
> umm, what?
> Did you mean write graphql backend using vibe.d?

Vibe-d web app -> Vibe-d/GraphQL gateway server (a la Prisma 1) -> Vibe-d/GraphQL API server -> Data.

That's why I'm more interested in the workings of the package than a "How-To get a basic vibe-d/graphql server. I want to know which pieces are available OOTB to be put together to create the above, and which pieces need to be created.

On Friday, 18 December 2020 at 02:46:32 UTC, Trustee wrote:
> On Thursday, 17 December 2020 at 14:49:42 UTC, evilrat wrote:
>> On Tuesday, 15 December 2020 at 16:25:29 UTC, Trustee wrote:
>>>
>>>connect a basic vibe-d app to a graphql backend.
>>>
>>
>> umm, what?
>> Did you mean write graphql backend using vibe.d?
>
> Yes. But more so, I want to learn the ins and outs of the graphqld package. What's contained, what isn't (in terms of what functionality available and/or possible - e.g. client gen???, xSQL gen), what to build to add to complement/contribute to the package. The first phase, docs.
>
> I have already begun working through the code and it's beginning to make sense.
>
> To be fair it's more about my fluency in D than the package itself. I haven't been coding for a while so it gets kinda rusty.
I'm also familiar with GraphQL in Node.js. The issue I find with graphqld package is their selection of terminologies (+ how the code is written). The code is also a test so it uses all the features of the package and not necessarily the essentials. So it will take some time to figure it out...including reading the original source code of the package.

My current understanding is it uses vibe.d to serve some static data. It does some validation of schema among other things and since the example meant as a development guinea pig, it uses all the API.... spread throughout the code.

I've not given it much time to filter those out myself. Will take a look once more after watching his DConf video about it....something about all spreadsheets must die.

> Any help would be appreciated though.
Hit me up in the dlang discord... @aberba

On Friday, 18 December 2020 at 03:36:05 UTC, Trustee wrote:
> On Thursday, 17 December 2020 at 14:49:42 UTC, evilrat wrote:
>> On Tuesday, 15 December 2020 at 16:25:29 UTC, Trustee wrote:
>>>
>>>connect a basic vibe-d app to a graphql backend.
>>>
>>
>> umm, what?
>> Did you mean write graphql backend using vibe.d?
>
> Vibe-d web app -> Vibe-d/GraphQL gateway server (a la Prisma 1) -> Vibe-d/GraphQL API server -> Data.
>
> That's why I'm more interested in the workings of the package than a "How-To get a basic vibe-d/graphql server. I want to know which pieces are available OOTB to be put together to create the above, and which pieces need to be created.

Heres's a demo I put together https://github.com/aberba/graphqld-demo

A minimal example with only the essential APIs

On Tuesday, 22 December 2020 at 23:49:12 UTC, aberba wrote:
> On Friday, 18 December 2020 at 03:36:05 UTC, Trustee wrote:
>> On Thursday, 17 December 2020 at 14:49:42 UTC, evilrat wrote:
>>> On Tuesday, 15 December 2020 at 16:25:29 UTC, Trustee wrote:
>>>>
>>>>connect a basic vibe-d app to a graphql backend.
>>>>
>>>
>>> umm, what?
>>> Did you mean write graphql backend using vibe.d?
>>
>> Vibe-d web app -> Vibe-d/GraphQL gateway server (a la Prisma 1) -> Vibe-d/GraphQL API server -> Data.
>>
>> That's why I'm more interested in the workings of the package than a "How-To get a basic vibe-d/graphql server. I want to know which pieces are available OOTB to be put together to create the above, and which pieces need to be created.
>
> Heres's a demo I put together https://github.com/aberba/graphqld-demo
>
> A minimal example with only the essential APIs

Thank you for this. Between this and the test code I should have enough to get going with.

I did also begin working through the test code and it was beginning to make sense. Being pushed for time though, I did spin up a Prisma 2 based gateway server. This time with the intention to build out a D version in parallel as I learn the package.

This should speed things along.

I will keep you posted on any developments and I'll be sure to get in touch if I have any questions.

Thanks again.

On Wednesday, 23 December 2020 at 08:33:21 UTC, Trustee wrote:
> On Tuesday, 22 December 2020 at 23:49:12 UTC, aberba wrote:
>> On Friday, 18 December 2020 at 03:36:05 UTC, Trustee wrote:
>>> [...]
>>
>> Heres's a demo I put together https://github.com/aberba/graphqld-demo
>>
>> A minimal example with only the essential APIs
>
> Thank you for this. Between this and the test code I should have enough to get going with.
>
> I did also begin working through the test code and it was beginning to make sense. Being pushed for time though, I did spin up a Prisma 2 based gateway server. This time with the intention to build out a D version in parallel as I learn the package.
>
> This should speed things along.
>
> I will keep you posted on any developments and I'll be sure to get in touch if I have any questions.
>
> Thanks again.

I keep hearing about Prisma too... gotta learn myself.