Jose Segura
11/01/2019, 9:32 PMArcticSpaceFox
11/01/2019, 9:33 PMArcticSpaceFox
11/01/2019, 9:35 PMmanagementApiSecret
and the add the secret in your prisma.ymlArcticSpaceFox
11/01/2019, 9:36 PMtechnicallynick
11/01/2019, 10:24 PMtechnicallynick
11/01/2019, 10:56 PMCharlie Pyle
11/01/2019, 11:15 PMMatthias Goossens
11/02/2019, 10:11 AMprimsa init
and configure my mongodb db but I get the INVALID_URL errorMatthias Goossens
11/02/2019, 10:14 AMAman
11/02/2019, 3:35 PMdeactivateduser
11/02/2019, 5:38 PMimages: [String]
result in Valid values for the strategy argument of '@scalarList' are: RELATION.
? Ok I need to add @scalarList(strategy: RELATION)
and I need to find out why lolcsamu
11/02/2019, 8:30 PMEhsan Sarshar
11/03/2019, 10:30 AMEhsan Sarshar
11/03/2019, 10:32 AMEhsan Sarshar
11/03/2019, 10:32 AMEhsan Sarshar
11/03/2019, 12:32 PMArcticSpaceFox
11/03/2019, 1:48 PMprisma2 lift save --name "Init"
I get the error that there is no schema.prisma
file. I do have a project.prisma
file, but do I have to rename that? I am confused. Also, I am very excited about mongo intergration in prisma2ArcticSpaceFox
11/03/2019, 1:55 PMprisma2 generate
I get Couldn't find prisma.schema
. I am so confused, especially since I am copying the steps from Nikolas Burk @ GraphQL Conf 2019Luke
11/03/2019, 3:09 PMprisma2-preview
channelLuke
11/03/2019, 3:10 PMJohn
11/03/2019, 3:33 PMJohn
11/03/2019, 3:34 PMDeploying service `freshboston` to stage `dev` to
server `prisma-us1` !
ERROR: Syntax error while parsing GraphQL query. Invalid input "{\n id: ID! @id\n title: String!\n description: String!\n image: String\n largeImage: String!\n price: Int!\n /", expected ImplementsInterfaces, DirectivesConst or FieldDefinitions (line 8, column 12):
type Items {
^
{
"data": {
"deploy": null
},
"errors": [
{
"locations": [
{
"line": 2,
"column": 9
}
],
"path": [
"deploy"
],
"code": 3017,
"message": "Syntax error while parsing GraphQL query. Invalid input \"{\\n id: ID! @id\\n title: String!\\n description: String!\\n image: String\\n largeImage: String!\\n price: Int!\\n /\", expected ImplementsInterfaces, DirectivesConst or FieldDefinitions (line 8, column 12):\ntype Items {\n ^",
"requestId": "us1:ck2j5im78jcbf0b606t86s244"
}
],
"status": 200
}
John
11/03/2019, 3:35 PMtype Items {
id: ID! @id
title: String!
description: String!
image: String
largeImage: String!
price: Int!
//createdAt: DateTime! @createdAt
//updatedAt: DateTime! @updatedAt
//user: User!
}
John
11/03/2019, 4:08 PMJohn
11/03/2019, 4:08 PM(node:45627) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
Jizong
11/04/2019, 2:16 AMconst array = ["a","b","c"] const string = `${array} is an array`
Jizong
11/04/2019, 2:16 AM["a","b","c"] is an array
Jizong
11/04/2019, 2:16 AMa,b,c is an array
Darryl
11/04/2019, 12:25 PMTim Holmes-Mitra
11/04/2019, 4:43 PMgraphql-import
to play nice with my custom Date scalar running on node + TS. I have four files in my setup with root.graphql
as the entry point as so:
# import * from "common.graphql"
# import * from "queries.graphql"
# import * from "mutations.graphql"
type Query {
root: String!
}
type Mutation {
root: String!
}
scalar Date
And the other files are as you would expect. I'm trying to combine my typeDefs as follows:
const typeDefs = importSchema("./src/interfaces/graphql/schema/type-defs/root.graphql")
...
// create ApolloServer
When I run my code this way I get the fol error: UnhandledPromiseRejectionWarning: Error: Query.getProfile defined in resolvers, but not in schema
. On console.log(typeDef)
it doesn't appear to have loaded the imports because the string only contains whats in root.graphql. I have tried relative paths similar to the path used in importSchema but no joy#. So in playing around I tried:
const schemas = {
common: importSchema("./src/interfaces/graphql/schema/type-defs/common.graphql"),
mutations: importSchema("./src/interfaces/graphql/schema/type-defs/mutations.graphql"),
queries: importSchema("./src/interfaces/graphql/schema/type-defs/queries.graphql"),
}
const typeDefs = importSchema(
"./src/interfaces/graphql/schema/type-defs/root.graphql",
schemas
)
Which gives the follow error: Error: Field starts: Couldn't find type Date in any of the schemas.
. If I remove the custom scalar type it runs correctly (or if I put everything into one .graphql file), but for obvious reasons I'd like to use custom scalars and split it into separate files.
Any suggestions?