@U077BEWNQ Thanks for trying to hack it with me. Firstly, I was referring to lacinia-pedestal because with that you didn't need to border about graphiql and it comes served. I would like us to have something like that here also, (a possibility of hacking that into ours using mount, not sure yet how to do it or if it is a good idea). That said, I am using luminus +graphql, setup a simple schema, resolversusing the inbuilt star-war schema we have named schema.edn. I could execute post and get graphql requests to get normal json response. But with the graph-i-ql, its a challenge, and even if I manage to read and run it somehow, am not sure how the queryroot will pick it up so that autocomplete suggestions and doc explorer works fine...

Do you have any online repo project you can share maybe?

The one I've got is probably already too big to be of use, plus I'm doing a bunch of funky stuff with auto-generating the schema (& sample data) from specs. But graph-i-ql should already be working if you're starting from luminus +graphql. What happens if you go to in your browser and open the docs explorer? Do you get an error? If so, what?

The two ends of the built-in graphiql setup (in luminus +graphql) are: Server: the /api service route defined in routes/services.clj Client: the graphQLFetcher function in resources/templates/graphiql.html.

The request structure seems odd to me, which is something to be aware of -- it's using a top-level :graphql-query key on the request, rather than putting it in params or body (which is what I'd expect on a POST).

[EDIT - posted cljs fn but I think it's still broken, so deleting]

When I visited localhost:3000/graphiql, I got the window alright... but Doc explorer is indicating NO SCHEMA AVAILABLE

Sounds like probably an issue with your schema. If you checkout the original version that was produced by the template, it should be working -- maybe just step forward from there or git bisect to find the change that broke it?

Just in case you haven't, you may have to restart the project or something to make sure your schema gets recompiled with the changes you've made. FWIW, here's my schema:

{:queries
 {:company_by_id
  {:type :Company,
   :args {:id {:type Int}},
   :resolve :query/company-by-id},
  :company_by_name
  {:type :Company,
   :args {:name {:type String}},
   :resolve :query/company-by-name},
  :company_by_group_name
  {:type :Company,
   :args {:group_name {:type String}},
   :resolve :query/company-by-group-name}},
 :objects
 {:Module {:fields {:id {:type ID}, :name {:type String}}},
  :Email {:fields {:id {:type ID}, :addresses {:type (list :String)}}},
  :Filter {:fields {:id {:type ID}, :name {:type String}}},
  :Location {:fields {:id {:type ID}, :name {:type String}}},
  :Company
  {:fields
   {:id {:type ID},
    :name {:type String},
    :group_name {:type String},
    :alias {:type :Email},
    :locations {:type (list :Location)},
    :modules {:type (list :Module)}}}}}

I've got to run for a few hours. It may be too much unrelated stuff to wade through, but just in case it would be helpful, here's my project in its current state (complete w/ git history): http://home.novonon.com/shortterm/infusion.zip

Good luck! I may be able to check back in later in case you have other qs I can answer.

OK, back for a bit. Looks like you graphiql (at least the luminus implementation) ALSO puts the query in the body, and it looks like that's the one that counts. Not sure why it also makes it a top-level key of the request. But I'm not that knowledgeable about http request/response stuff, maybe there's a good reason 🤷

Huh. I guess it just puts it in the body, and then (as an artifact of cljs-ajax?) it's available as a top-level key/val on the request.

Oh, I see, it's a piece of middleware that my colleague added that slurps the body and assoc-es it onto the request. So that's specific to my project.

Nope, sorry, my mistake again -- that's there in the template:

(defn wrap-graphql
  "If the request body contains an InputStream, reads the query, parses the json,
  and puts the resultant map into the request under the key :graphql-query."
  [handler]
  (fn [{:keys [body] :as req}]
    (let [data (cond
                 (instance? BytesInputStream body) (slurp body)
                 (string? body) body
                 :else nil)]
      (if data
        (handler (assoc req :graphql-query data))
        (handler req)))))

Anyway, hope I'm not confusing you more than I'm helping 😉

Thanks for the detailed explanation... I managed to use the weekend to hack around your project...

And I discovered that the +swagger conflicts with +graphql with the earlier superseding...

Would be nice to have them run side by side though, I don't know if that's a good option for the template @U050CBXUZ

I have a sample project: https://github.com/Okwori/graphqltest. The main advantage might be ease to run graphql query over rest client and ofc also via the graphiql. I could raise a pr if...

Ah yeah I think that should be pretty easy to fix

A pr would be most welcome :-)