Coverage increased (+0.4%) to 58.154% when pulling fa81cbc on tdurnford:1948 into 6f67e58 on Microsoft:master.

The change looks good. But the sample itself isn't quite, not your fault.

We shouldn't capture onKeyDown on the whole Web Chat. Very hacky sample.

Our sample is intended for our users to copy and it will work. I won't say it will be in production quality, but they can't be hacky too. Our sample is "our best practice to do one small thing at a time, in a very correct way". And it also serve as a teaching material for our users. Then we evaluate the feedback and may fold the code back into production.

If our sample is hacky, few things would happen:

• Devs spot we are hacky, they will not trust our product anymore
  • In recent years, I saw devs upset about quality of our samples/documentations and complaining on social media, and more people start leaving our platform
• Devs don't know it is hacky, when they aggregate multiple samples together, everything will start falling apart
• We cannot fold the sample code back into our product
• Devs learn wrong thing, and the ripple effect, they will pretty soon start creating a monster that is difficult to maintain for them

On one side, to me it's a smaller side, I am worried about product quality will drive users away.

On the other side, which is bigger to me, I am worried about devs training and quality. If they can do better at their job, they will be able to create a more sounding solution that would evolve and last.

And to me, being passionate about customers, teach them, advocate great things, empower them, is something in Microsoft's DNA. We ran MSDN documentation and it was every dev's go-to place to learn things. The community changed, MSDN changed, but the spirit never.

Too much whine.

The better solution for this sample, one (baby) step at a time:

• Build a React component, independent of Web Chat, that would work with history using up/down arrow, etc.
  • It doesn't need to be live inside its own repository or package
• Build a simple React app that works with this component, still, independent of Web Chat
• Improve the React component by trying out both <input> and <textarea> (multiline)
• Build and customize Web Chat, modify send box and replace <input> with this component

For production quality, add automated tests, wrap the component nicely, etc.