From 2d145b026cfdf54a63bef0b9d6324b6785390307 Mon Sep 17 00:00:00 2001 From: Wes Bos Date: Fri, 14 Sep 2018 12:18:12 -0400 Subject: move finished folder --- stepped-solutions/FINISHED/frontend/notes.md | 36 ---------------------------- 1 file changed, 36 deletions(-) delete mode 100644 stepped-solutions/FINISHED/frontend/notes.md (limited to 'stepped-solutions/FINISHED/frontend/notes.md') diff --git a/stepped-solutions/FINISHED/frontend/notes.md b/stepped-solutions/FINISHED/frontend/notes.md deleted file mode 100644 index 9ea38ef..0000000 --- a/stepped-solutions/FINISHED/frontend/notes.md +++ /dev/null @@ -1,36 +0,0 @@ -## Commonly Used Terms - -Mutation - -Query - -Scalar - this means that it's an acutal value and not a relationship. A scalar type of ID might be ABC123, a scalar type of String might be "Wes Bos". These are the default scalar types: - -Int: A signed 32‐bit integer. -Float: A signed double-precision floating-point value. -String: A UTF‐8 character sequence. -Boolean: true or false. -ID - -## The process for adding a new field: - -1. First we need to add the field to our type in datamodel.graphql -2. Then, we need to add it to our schema.graphql file, which is how we define our GraphQL API. Here we will only include the fields that we want to be query-able -3. Now the database needs to know about the new field, so we run `prisma deploy` - -## The process for adding a new type - -1. First we need to add it to the database. Edit datamodel.graphql: - -```js -type Item { - id: ID! @unique - title: String! - description: String! - price: Int! -} -``` - -2. Now we need to either re-define it in our client-side schema, or import it carte blanche - -## The process for adding new queries or mutations -- cgit v1.3