Prisma

Yea not sure, sorry I can't help any more than I did :slightly_smiling_face:

I'm getting that the cert date is invalid

I just went there and got the same error though, so you are definitely onto something

<@U0RQY0KK5> Sounds like a major issue with the certs

SSL cert must have just expired or something

<@U54M9GFLH> <@U76JB2KL5> <@U5FTM4GQL> thanks, looking into it now! 

<@U54M9GFLH> <@U76JB2KL5> <@U5FTM4GQL> <@U6S4E7T4K> <@U49V8B8TF> <https://twitter.com/GraphcoolStatus/status/910752705647464448>

we're in contact with our hosting provider who's looking into the issue - looks like the renewal of the certificate failed for an unknown reason.

:+1: Thank you for your quick response. Hopefully they resolve it soon. :blush:

It's now resolved, thanks! <https://status.graph.cool/>

Is there a simple way to query the db from inside a schema extension?

The easiest way is to use graphcool-lib. In a schema extension, you can construct an instance from the event:

const fromEvent = require('graphcool-lib').fromEvent

module.exports = function(event) {
  
  return api.request(`
	query {
		[GraphQL Query Here]
	}
  `)
  .catch((error) =&gt; {
        return { error: error.toString() }
      })
  
}

You just saved me a couple hours implementing a webhook

Apologies for the simple question, just starting out... I'm having trouble understanding how I can update something in the graph.cool data - I have `type Item { id ID! @isUnique connected: Boolean }` and I'd like to toggle `connected` - What would the query be to do so?

To change data on the server, you use GraphQL mutations. In this case, you will want to use the updateItem mutation

I think the part that is confusing me is the `updateItem` bit -- does graph.cool (or graphql) automatically 'add' add&lt;name&gt; update&lt;name&gt; delete&lt;name&gt; or is that something I'm supposed to be setting up somewhere?

Yes, Graph.cool generates a whole load of mutations for your API. For every type X you will have createX, updateX and deleteX

(doesn't have to actually toggle, I basically just want to set it to `true`)

-.js

<@U75D1TYTH> `async`/`await` is currently not supported in functions. we're working on it!

<https://github.com/graphcool/graphcool/issues/227>

Untitled.js

Changed to the above, getting the same error

<@U75D1TYTH> you got `await` in your code (line 12)

It appears to be happening before getting to the request

you need to say `simple/v1` instead of the string you passed in

<https://github.com/graphcool-examples/functions/blob/master/authentication/facebook-authentication/facebook-authentication.js#L6>

replace `<https://api.graph.cool/simple/v1/cj7mnyihh05nl01453hnia715>` with `simple/v1`

Looks like my event object doesn't have the "graphql" object in eventcontext

```
"use latest"
const fromEvent = require("graphcool-lib").fromEvent;

module.exports = function (event) {
  	const api = fromEvent(event).api("simple/v1");
  	const query = `
		allDataSources {
			id
		}
	`;
  
  	return api.request(query)
  		.then(function (result) {
    		return {
            	data: {
                	dataSourceIds: ["hello", "schema"]
                }
            };
    	})
};
```

`const { fromEvent } = require("graphcool-lib");` needs to say `const fromEvent = require("graphcool-lib").fromEvent;` I believe

did you create root token with the same name as the function? (formerly called permanent authentication token)

&gt; Create a new Permanent Access Token (PAT) in project settings. It needs to have the same name as the function to make it available in the execution context of the function.

<https://github.com/graphcool-examples/functions/tree/master/authentication/facebook-authentication#setup-the-authentication-function>

only in the function examples (we're currently revisiting our docs)

Does that need to be copied anywhere in the function source?

(I created the PAT with matching name "validDataSources") and still getting same error

```
type ValidDataSourcesPayload {
  dataSourceIds: [String!]!
}

extend type Query {
  validDataSources(componentTypeId: String!): ValidDataSourcesPayload
}

```

it's probably because you are executing test run and it's not setting the context correctly

can you try to run it from the Playground instead?

```
{
  "data": {
    "validDataSources": null
  },
  "errors": [
    {
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "validDataSources"
      ],
      "code": 5000,
      "message": "A function returned an unhandled error. Please check the logs for executionId 'us-west-2:simple:cj7u3qjj3r6h401324kojkqt2'",
      "requestId": "us-west-2:simple:cj7u3qjj3r6h401324kojkqt2"
    }
  ]
}
```

your query needs to say `query { allDataSources { id } }`

Is there a good way to debug schema extensions?

you can see the logs in the functions view

with the new CLI, you can hook into the log stream

I'll share a link to the forum thread when it's back up... :slightly_smiling_face:

What do you think if we can make the Permission part into code instead of click and click in the dashboard?

the forum is actually down but I think it was two days ago the new CLI in beta as been announced and you can manage your permissions and everything from you project with it. Actually you don’t use the console.graph.cool anymore (just to visualise your data if you want)

you can download use the new CLI with `npm install -g graphcool@beta` and then you have the `graphcool init` command to dump all your projects in files in your codebase :wink:

<@U75B95PEH> I'll share the forum post as soon as possible - you should read it before installing and using the CLI :slightly_smiling_face:

<@U5Z2AG74M> Wow, thanks for sharing, Ill have a try.

But guys, it would be better to have more docs about it. It works fine to me, awesome work!

It’s still in beta now, I’m sure there is more doc coming

<@U75B95PEH> check <https://www.graph.cool/forum/t/feedback-new-cli-beta/949?u=nilan> for more information :slightly_smiling_face:

Thanks <@U5Z2AG74M>, I just have a feedback about the query files. I would suggest to use some name convention instead of hash, like Type-operation(User-read.graphql), the hash file name really bothering me in the text editor...

<@U0RQY0KK5> great the forum is online again
<@U75B95PEH> I was thinking the same but the file will be terrible because you cannot constrain with just type + operation, sometime you want to have specific permissions for fields and you can have multiple `user-read` in this case so I think just name your file is the most flexible way.

I can manage them at my end, once its code, I have the control anyway, but just please think about it.

<@U75B95PEH> could you add this comment to the Forum? :slightly_smiling_face:

yes i will answer it :wink: I have a good architecture wich is quite clear and you may like it

I do like the way working with the CLI tool for Schema

Are schema extensions pullable/editable via CLI?