following those directions, I did get a graphic-config is not in the register error when attempting to npm link it

I'll ping you via DM 🙂

is the site down? I’m getting a 503 error at https://www.graph.cool/docs

Seems like our hosting provider is having challenges. We are looking into it. This doesn’t affect the api.

Homepage and docs are online again.

on https://www.graph.cool/ there's a schema demo with instagram/pokemon/airbnb, where there's a selector between "visual" and "IDL", but clicking IDL does nothing

Thanks @sdubois We wanted to get the new website out there as early as possible. Now we have a list of stuff to catch up on. I’ll ad this to the list 🙂

Hey there! My GraphQL talk at ng-be in Ghent Belgium went great. Got great feedback from people. I covered GraphQL queries, mutations and subscriptions! This is a url to the slides http://slides.com/gerardsans/ng-be-unleashing-the-power-of-graphql ✨ 🚀

why can’t you use id as an argument in a nested query? e.g.

{ user { posts(filter:{id:$nodeId}){  id } }}

works, but

{ user { posts(id:$nodeId){  id } }}

does not work but

{ posts(id:$nodeId}{ id }}

does work

does the id argument only work on top level objects in the query? Maybe you can point me to the page in docs that lists out the query arguments and their types? Or is that general conventions that I can look at graphql docs for

The toplevel field:value syntax is only for fields that return a single element instead of a list. So in your example I think you mean

{ Post(id:$nodeId}{ id }}

instead of

{ posts(id:$nodeId}{ id }}

So yes, it only works on top-level, and only for unique fields, such as the id field

this is the relevant passage in the docs: https://www.graph.cool/docs/reference/simple-api/one-node#specifying-the-node-by-another-unique-field (Simple API) 🙂

ok thanks, in this case it would still be posts since I’d be looking through the relation on the user object - trying to work through the query permission examples and tinkering with it

@nilan thanks! I keep forgetting that I have to click on “Simple API” for the rest of the docs

cool. Yeah, you would have to use the filter syntax in that case. Happy to help design specific Permission Queries if you get stuck at some point

so looking at the rules permissions beta - if I’m trying to add a rule to the user so that only they see their own private fields - I tried adding this rule:

{
  user(filter:{id:$nodeId}){
    id
  }
}

but it doesn’t seem to save

and I’m getting red squigglies in the rule editor window

so, do you really want to use

nodeId

there? shouldn't it be rather

userId

?

um yeah sorry userid

and if you hover over the red lines with your mouse, what is the error message?

no message

doesn’t seem to trigger a hover

with user I can’t use

user(id:$userId)

right?

and I have to use the filter?

you have to use the filter

Or are you referring to the top level user field? That one doesn’t support filter either as it alway returns the current user.

If your rule is that a user can only se its own fields your query would look like this:

{
  allUsers(filter:{AND:[
    {id:$nodeId},
    {id:$userId}]})
  {id}
}

Hey there <!channel>! We've just announced Learn Apollo. 🎉 graphql Read here for more: https://dev-blog.apollodata.com/learn-apollo-build-graphql-apps-with-react-react-native-or-exponent-4787269a4747

^^ ok