Tk/issue14

[flex2016]

PR Checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #14

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[ x] No

Other information

[netlify]

✅ Deploy Preview for reachat-storybook ready!

Name	Link
🔨 Latest commit	218f882
🔍 Latest deploy log	https://app.netlify.com/sites/reachat-storybook/deploys/66cdd274d6a4af0008a17cdc
😎 Deploy Preview	https://deploy-preview-41--reachat-storybook.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[flex2016]

@amcdnl and @steppy452

[steppy452]

@flex2016 thanks for taking the time and working on this! This is a great start - it seems like there's a good base for the styling of the component. One thing we might need to align on is the requirements for the follow up message.

The idea is that the follow up responses are like "quick reply" prompts for the user to choose from. So, in your example, possible follow up prompts could be "What are some downsides of React?" and "What are alternative options to React?" and if the user clicks on one of those options, it would continue the conversation as if the user typed it in.

[steppy452]

I think here instead of an either or here, we would always show the <MessageResponse /> and optionally show <FollowUpResponse /> if some exist

[flex2016]

@steppy452 Thank you for clarifying the requirements. Please review the changes I have made. Also, regarding the image, what are we expecting the image payload to be? Currently, I have it as a URL.