Fork me on GitHub
#graphql
<
2018-09-12
>
pfeodrippe03:09:55

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?

mattly03:09:09

What do you mean, “hidden from the schema”?

mattly03:09:31

GraphQL doesn’t really support that

mattly03:09:16

You could setup a different endpoint with the other query roots and mutations defined

mattly03:09:33

Or make a certain level of authentication required

pfeodrippe03:09:48

Understood, @mattly, thanks!

mattly03:09:44

if you're trying to keep the API "secret" because of some domain entity or whatnot, probably best to setup a second endpoint

mattly03:09:51

do authenticate it though

mattly03:09:57

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)

pfeodrippe04:09:53

Hunnn, gonna try to use it, it appears to be a good plan! Gracias, @mattly o/

hlship21:09:38

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.

👍 8
🙏 8