zonofthor
05/09/2018, 2:19 PMpettanko
05/09/2018, 6:47 PMjangerhofer
05/09/2018, 7:49 PMprisma deploy
command no longer generates a schema file for the GraphQLServer
instance to ingest via the typeDefs
property. Do I understand correctly that deploy
should be generating that file according to .graphqlconfig.yml
?johhansantana
05/09/2018, 8:42 PMYour token is invalid. It might have expired or you might be using a token from a different project
after upgrading to 1.8?gabe.bravo
05/10/2018, 1:58 AMJim
05/10/2018, 3:06 AM$ prisma deploy
warning prisma.yml: "cluster", "service" and "stage" are deprecated and will be replaced with "endpoint".
To get the endpoint, run prisma info. Read more here: <https://bit.ly/migrate-prisma-yml>
Created docker-compose.yml with a local prisma server.
Please run $ docker-compose up -d to start your local prisma.
Note: prisma local start will be deprecated soon in favor of the direct usage of docker-compose.
$ docker-compose up -d
WARNING: Found orphan containers (database_mysql_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
database_prisma_1 is up-to-date
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
edc498e32eaf prismagraphql/prisma:1.8 "/bin/sh -c /app/sta…" 12 minutes ago Restarting (1) 16 seconds ago database_prisma_1
8db6310c5861 mysql:5.7 "docker-entrypoint.s…" 18 hours ago Up About a minute 3306/tcp database_mysql_1
661efd2ad875 mysql:5.7 "docker-entrypoint.s…" 36 hours ago Up About a minute 3306/tcp temp_db_1
$ npm run start
> prisma-file-handling-s3@1.0.0 start /Users/jameschetwood/Projects/prisma/img-up-test/file-handling-s3
> dotenv -- nodemon -x ts-node -e ts,graphql src/index.ts
[nodemon] 1.14.11
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `ts-node src/index.ts`
Type "Node" is missing a "resolveType" resolver. Pass false into "resolverValidationOptions.requireResolversForResolveType" to disable this warning.
Server is running on <http://localhost:4000>
Request to <http://localhost:4466/file-handling-s3-example/dev>:
query:
query ($_where: FileWhereInput, $_orderBy: FileOrderByInput, $_skip: Int, $_after: String, $_before: String, $_first: Int, $_last: Int) {
files(where: $_where, orderBy: $_orderBy, skip: $_skip, after: $_after, before: $_before, first: $_first, last: $_last) {
id
url
name
size
secret
contentType
}
}
operationName: null
variables:
{}
[Network error]: FetchError: request to <http://localhost:4466/file-handling-s3-example/dev> failed, reason: connect ECONNREFUSED 127.0.0.1:4466
Error: request to <http://localhost:4466/file-handling-s3-example/dev> failed, reason: connect ECONNREFUSED 127.0.0.1:4466
// Ive shortened this message
I now have a playground up at http://localhost:4000/ and it has access to my schema, but when I run a query I get an error:
{
"data": null,
"errors": [
{
"message": "request to <http://localhost:4466/file-handling-s3-example/dev> failed, reason: connect ECONNREFUSED 127.0.0.1:4466",
"locations": [
{
"line": 2,
"column": 3
}
],
"path": [
"files"
]
}
]
}
arturgvieira
05/10/2018, 3:54 AMarturgvieira
05/10/2018, 3:55 AMarturgvieira
05/10/2018, 3:55 AMarturgvieira
05/10/2018, 3:59 AMarturgvieira
05/10/2018, 3:59 AMKyleG
05/10/2018, 4:49 AMctx.db.query.user(...)
. It looks for a user with a particular id
as the query argument. I know how that is defined, so I don't need help with that.
But it's the query fields I'm lost on. For example, if the query looked like this:
me {
id
email
}
Those fields id
and email
I figure are defined in the info
variable. But printing that variable to console doesn't reveal much other than it's a big hairy object that's difficult to read.
How do I define and run my own queries internally? Say I wanted to write a query internally that checks something for me?
The way I've learned GraphQL is through tutorials and example code, so to change things I struggle. And it's hard to Google around for this stuff! I imagine the answer might involve graphql-tag's gql
template literal (https://github.com/apollographql/graphql-tag), which I'm familiar with when using Apollo in my client... but I need hints.Jim
05/10/2018, 5:00 AMuser
05/10/2018, 5:10 AMkitze
05/10/2018, 5:30 AMKhoa Huynh
05/10/2018, 6:35 AMnilan
05/10/2018, 7:14 AMmurra
05/10/2018, 7:58 AMmurra
05/10/2018, 7:58 AMmurra
05/10/2018, 7:59 AMmanu
05/10/2018, 10:13 AMdouglaseggleton
05/10/2018, 10:32 AMwoss
05/10/2018, 10:47 AMWhoops. Looks like an internal server error. Search your server logs for request ID: eu1:management:cjh0ersv75ech0b84ga53mgj3
can’t deploy to prisma.shalexc
05/10/2018, 11:21 AMLotafak
05/10/2018, 11:42 AMprisma_1 | Caused by: java.sql.SQLNonTransientConnectionException: Could not connect to address=(host=db)(port=3306)(type=master) : Connection refused (Connection refused)
.
I noticed, that the db
container is probably not yet running, so the prisma can’t connect to it. Is there a way to extend waiting time?weakky
05/10/2018, 1:52 PMdeleteManyVariants()
here? Message: The change you are trying to make would violate the required relation '_VariantOnSelectedOptions' between SelectedOption and Variant, Location: [object Object], Path: deleteManyVariants
wesbos
05/10/2018, 1:57 PMError: Cannot return null for non-nullable field CartItem.id.
for a simple mutation - I’ve found a few older threads about this but I wanted to see if you had ideas on what this might beuser
05/10/2018, 1:59 PMpettanko
05/10/2018, 3:16 PMwesbos
05/10/2018, 3:16 PM