From 8a5825d52271d712ec7c8348447d433067e13ef2 Mon Sep 17 00:00:00 2001 From: Wes Bos Date: Thu, 13 Sep 2018 14:18:56 -0400 Subject: DONE --- stepped-solutions/FINISHED/frontend/notes.md | 36 ++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create 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 new file mode 100644 index 0000000..9ea38ef --- /dev/null +++ b/stepped-solutions/FINISHED/frontend/notes.md @@ -0,0 +1,36 @@ +## 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