feat: add adaptive-form and extension packages

[a-b-r-o-w-n]

Reasoning

Currently, the app is mainly driven by a single static schema file (appschema.ts). This has worked well up until now by giving us a fixed point of reference to build against, but in order to work with the current form library, we have had to make modifications that deviate from the true sdk schema.

As we approach GA, we need to start supporting multiple versions of the sdk schema as well as schemas that have additional custom components, which means that the bot project's schema needs to drive the UI experience. This set of changes enables that, as well as introducing some new concepts as well as modifying some existing patterns.

New Concepts

Extension

The extension package is a shared set of utilities that provide apis to create composer extensions / ui-plugins. It currently has a small surface area, but the intention is that it can grow as composer's capabilities expand.

It exports a few utilities so far:

• <Extension /> component which is meant to be rendered in Composer and provides a context for extensions to consume.
• useShellApi is a hook that provides shell data and shell apis to any component in an extension or ui-plugin.
• Typescript interfaces that are shared across extensions and ui-plugins.

Adaptive Form

This is a replacement for the obiformeditor package that re-implements the underlying json schema form renderer, with modifications and customization to support the composer forms UI/UX. It borrows many ideas from the json schema form library but has a smaller interface that is more tailored to our form usage at this point in time. The new pattern this enables is the usage of a ui plugin.

UI Plugin

A UI plugin is a framework that developers can use to change / extend composer form functionality. It is heavily based on the ui schema idea from the json schema form library, but adds some additional capabilities such as registering new recognizer types and providing a way to customize the form based on the schema $role property.

This should be integrated with the visual designer's ui schema in the future so that the whole editing surface can be customized within a single plugin architecture.

@monaco-editor/react

This change also switches the monaco react editor package to one that does not require a webpack plugin to work with our custom language servers. It was a drop-in replacement for the most part, with some minor api changes.

Consolidation of types into @bfc/shared

In an effort to make sharing of types more effective, I've moved types from @bfc/indexers into @bfc/shared. This allows other packages to take dependencies on the types defined in the indexers without the dependency on the indexers themselves. This probably introduced more churn than necessary, sorry!

Future

I attempted to minimize the churn in the Composer core while laying the ground work for future refactors. I'll jot down some ideas below:

• Refactor visual designer to use extension pattern (refactor visual designer to use extension pattern #2120)
• Remove the extension container / iframe embedding. Hoist extension rendering to composer core. -- This idea has not been fruitful to us and by eliminating it we are freed to make more performance enhancements. (do not use iframe to embed extensions #2121)
• Make the extensions themselves not require props -- just use the extension context to get data, etc. This will require some work in the extension to re-render when the shell data / apis change.

Links

Closes #2119
Closes #1974
Closes #1975

#664
#2120
#2121

Authors

@a-b-r-o-w-n
@tdurnford

[cwhitten]

seeing the following:

1. selecting the LUIS recognizer throws an alert?

2. deselecting and reselecting a response node doesn't render the content in the form

3. Switch condition, adding cases renders Unsupported field

4. Choice input, can't see full option text (should we default to something other than expression)?

[github-actions]

Coverage increased (+0.5%) to 40.185% when pulling fa78ee4 on a-b-r-o-w-n:feature/adaptive-form into 2cc7ec4 on microsoft:master.