This is a mapping between the names of the GraphQL fields (“a_name_like_this”) and the keyword keys of the maps being selected (:a-name-like-this).
Otherwise, if you want snake-case names in your GraphQL you have to provide an explicit resolver for every single field, no matter how trivial.
What is “it goes wrong”? Does the service not start? Does it not handle requests? Is there some issue with the mapping of the container’s port to a host port?
It did not handle the request, and was indeed the hostname I had to change. https://github.com/gklijs/bob2021 is all updated and aside from the docs ready for BOB the 26th. I might also send a pr to change ‘my’ demo project in the lacinia from open-bank-mark to this.
0.39-alpha-1 just hit; I'm working on extending things so that you can navigate around the schema to see types, fields, arguments ... and eventually, other things, such as union members, interface implementers, etc.
We're using it to automatically generate an "uber-query" that selects all fields below a starting query root.
Our generated Uber query is over 7000 lines, once formatted (parses in 65 ms). Find all the nooks and crannies in your query.
Alas, the code is ugly and not something I'd share, and doesn't handle a lot of cases (such as unions or interfaces).
Still a work in progress.
Very cool, keeping a close eye on all the selection stuff!
In minor news, found a little spec compatibility bug in lacinia. Left a PR with a fix and some relevant links, no rush tho :)
I can check it out soon. Thanks!