Matching logic completed

[tchan128]

Buddy matching logic is completed:

  graph TD;
      A[User submits conversation form]-->B[Searches for available, same expertise, listener];
      B-->C[No buddy found: Searches for available listener];
      B-->D[Buddy found and matched];
      C-->E[No buddy found: Return null]
      C-->F[Buddy found and matched]

In this logic, when the form is submitted here are the concurrent actions:

• The sharer starts a new conversation, populating conversation
• Listener is matched
• The conversation added to listener's conversation
• Listener's availability set to false

Example of matching shown here, both listerner and sharer will have the conversation so it can be populated on their dashboard:

Testing to see if other listeners with personal is matched (the answer is no):

Next step:

• [ ] Set both the listener and sharer's buddy field - so on My Bench we can populate conversation with ___

From today's discussion, once the form is submitted it should bring the user to the conversation component regardless of a match or not. If there is a match the conversation component can display connected with ____. If there isn't a match (null), component can display Finding a buddy, please take a seat first