Messages

[slightlytyler]

• [x] A user should be able to send a message directly
• [x] A user should be able to send a message in regards to a post
• [x] A user should be able to query for all their message chains
• [x] A user should be able to query a single message chain
• [ ] A user should receive notifications about their messages

[jacobhausler]

• do you have more specifics on what is required on the back-end for notifications?

Implemented as Conversations and Messages

type Conversation implements Node {
  id:ID!
  createdAt: Date!
  updatedAt: Date!
  subject: String
  refPost: Post @relationship(path:"<-REFERENCED-")
  users: User @relationship(path: "<=CHATTED=")
  messages: Message @relationship(path:"=HELD=>")

}

type Message implements Node {
  id:ID!
  createdAt: Date!
  body: String!
  author: User! @relationship(path:"<-AUTHORED-")
  chat: Conversation! @relationship(path:"<-HELD-")

}

[jacobhausler]

conversations are nodes, so for bullet 4

query{
  node(id:[id]){
    ... as Conversation{
      id
      subject
      users
      etc
    }
  }
}

[jacobhausler]

for all conversations:

query{
  session{
    currentUser{
      conversations{
        $conversationFragment
      }
    }
  }
}

[slightlytyler]

@jacobhausler we'll need to track if messages have been viewed or not and the be able to query for the number that haven't been

[slightlytyler]

Notification might be it's own type actually

[jacobhausler]

Need to figure out the logic of (post and message notifications separately):

• [ ] what fields need to be added to which types to track notifications?
• [ ] which existing mutations need to change the new fields?
• [ ] do we need to add new mutations?

[jacobhausler]

going to create 1 sendMessage mutation that takes an optional postId to satisfy 1 and 2

[jacobhausler]

are these email style conversations (many conversations between 2 users) or facebook (1 convo between 2 users); many would be easier

[jacobhausler]

email style conversations will use these two forms of the sendMessage mutation; i don't think we need you to be able to access Conversations directly if the following are true:

• users can have many conversations another user (a la email or reddit; one subject)
• posts/subjects are referenced at the Conversation level

##This one takes in optional params to create a new conversation; no chatID = new Conv.
mutation{
  sendMessage(input:{
    clientMutationId:"sendMessage to new conversation"
    toUserId:"ID of receiver"
    refPost: "ID of referenced post"
    subject:"test subject"
    body: "test message body"
  }){
    changedConversation{
      id
      subject
      users{
        id
        fullName
      }
      messages{
        id
        author{
          id
          fullName
        }
        body
      }
    }
  }
}

##This one takes in less params for an existing conversation
mutation{
  sendMessage(input:{
    clientMutationId:"sendMessage to existing conversation"
    body: "test message body"
  }){
    changedConversation{
      id
      subject
      users{
        id
        fullName
      }
      messages{
        id
        author{
          id
          fullName
        }
        body
      }
    }
  }
}