This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-12
Channels
- # beginners (63)
- # boot (3)
- # braveandtrue (153)
- # cider (19)
- # cljdoc (2)
- # clojure (80)
- # clojure-dev (25)
- # clojure-italy (73)
- # clojure-losangeles (1)
- # clojure-nl (4)
- # clojure-spec (67)
- # clojure-sweden (1)
- # clojure-uk (83)
- # clojurescript (56)
- # clojutre (11)
- # core-logic (37)
- # cursive (18)
- # datomic (14)
- # editors (10)
- # emacs (13)
- # figwheel-main (11)
- # fulcro (62)
- # graphql (11)
- # jobs (3)
- # klipse (1)
- # leiningen (6)
- # off-topic (91)
- # onyx (7)
- # pedestal (3)
- # portkey (5)
- # re-frame (14)
- # reagent (13)
- # remote-jobs (1)
- # shadow-cljs (111)
- # tools-deps (4)
- # yada (10)
Hi o/, I'm using Lacinia with pedestal (and enjoying it very much btw) and would like to make some mutations/queries hidden from the schema, is there some recommended way to do it?
Understood, @mattly, thanks!
if you're trying to keep the API "secret" because of some domain entity or whatnot, probably best to setup a second endpoint
for my project at $dayjob we provide the same graphql API for our app for our end-users and our customer-support folks, but some of the operations are privileged (and documented as such)
Hunnn, gonna try to use it, it appears to be a good plan! Gracias, @mattly o/
I'm getting closer to getting the latest Lacinia PRs into production here, which I try to do before each stable release. It's been long delayed due to vacation and other factors inside WalMart ... we're being very careful as this release changes the content of error maps to conform to the June 2018 GraphQL spec.