Saying goodbye to graphcool

1 files changed, 29 insertions, 1 deletions

diff --git a/notes.md b/notes.md
index 798953c..3b8c1da 100644
--- a/notes.md
+++ b/notes.md
@@ -28,7 +28,6 @@ import { Link } from '../routes';
 >
 ```
 
-
 ## Commonly Used Terms
 
 Enhancer - These are just high order components that "infuse" the data we want into our components via props
@@ -37,4 +36,33 @@ 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