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
