Re: [Chicken-users] GraphQL libraries coming soon

2019-07-25 Thread Lassi Kortela

On 25.07.2019 10.36, Mark Janssen wrote:
I am currently working on a GraphQL PoC at work. The chicken deployment 
story combined with GraphQL suppport would be very nice.


Great, welcome aboard! It's always exciting to get things done faster.

1. Think about N+1 early, most real life projects will need some sort of 
dataloader. It's nice if it's integrated.


You have much more background for thinking about query performance than 
I do, so all suggestions are warmly welcome.


2. Allow a schema first approach. This helps with interop, I have seen 
dotnet graphql schemas which are easily recognizable as such.


I don't understand what any of that means :)

Current repo here: .

We should find some communication channels so we don't spam 
chicken-users too much. I suggest we talk on the schemeweb mailing list 
(https://srfi.schemers.org/scheme-lists-subscribe.html). It aims to 
develop a portable Scheme web stack, so a GraphQL implementation would 
fit right in. It's very low-traffic ATM, so maybe more traffic would 
inspire more people to hack on web projects :) I personally like GitHub 
issues as well. Private email is fine. I don't normally use IRC but I can.


___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] GraphQL libraries coming soon

2019-07-25 Thread Mark Janssen


On Wed, Jul 24, 2019, at 17:54, Lassi Kortela wrote:
> We're exploring making a GraphQL API for the Schemedoc project 
> 
> 
> In case anyone wants to advise or to test this early for your own 
> project, let me know. 
> 

I am currently working on a GraphQL PoC at work. The chicken deployment story 
combined with GraphQL suppport would be very nice.

So I am very interested to look at this. Some ideas off the bat already:

1. Think about N+1 early, most real life projects will need some sort of 
dataloader. It's nice if it's integrated.
2. Allow a schema first approach. This helps with interop, I have seen dotnet 
graphql schemas which are easily recognizable as such.

Mark___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] retrieving a structure's symbol name

2019-07-25 Thread Peter Bex
On Thu, Jul 25, 2019 at 07:36:04AM +0200, Marco Maggi wrote:
> I am writing a library that mimics R6RS records.  Every R6RS record-type
> can  be associated  to a  unique identifier  (UID), which  is a  symbol.
> Defining the  same record-type  in multiple modules  is fine,  under the
> correct conditions.
> 
>   Using the  UID as  struct type  name, and  so implementing  records as
> simple CHICKEN structs, seems an efficient way to do it.

I had a quick look at the R6RS page and god that shit is ugly :)
But you're right, using these low-level constructors seems the best way
to do this.  Maybe you can use gensyms or uuids for the record names.
uuids probably work better if you later want to generate a types database
for the library.

Cheers,
Peter


signature.asc
Description: PGP signature
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users