Feature(Sharing): Introducing Promptable conversations

[ManishMadan2882]

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Backend

1. Made POST /api/share endpoint compatible with promptable sharings

   • If the api key is existing with the same attributes(prompt_id, chunks, source), shared conversation depends on that api_key. New shared conversation doc is created, responding with the UUID as identifier.
   • else if the api key is existing and a shared conversation document with exactly same fields is already existing, avoid re-creating the shared_conversation and return the pre_existing UUID as identifier.
   • generate a new api key, assign its key to the new shared conversation, respond with the new document's uuid.

2. Modified the GET /api/shared_conversation/<string:identifier> endpoint to send the api_key if present in response.

3. complete_stream() : Prevent storing request made through api_key

Frontend

• Structured the redux slice for sharedConversations.
  
• Integrated the stream route, for prompting through shared conversations' api-keys.
• Further queries after the originally shared ones, will be saved in localStorage
• Why was this change needed? (You can also link to an open issue here)
  Allow sharing conversations which can be prompted further

[vercel]

@ManishMadan2882 is attempting to deploy a commit to the Arc53 Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs-gpt	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 29, 2024 8:24pm

[dartpain]

All good, thank you!