Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: [not target master] rename 'uiSchema' in PluginConfig to 'formSchema' #2634

Merged
merged 2 commits into from
Apr 14, 2020

Conversation

yeze322
Copy link
Contributor

@yeze322 yeze322 commented Apr 14, 2020

Description

With this PR, ui plugins will use formSchema + flowSchema convention instead of a generic config name uischema.

@a-b-r-o-w-n I only touched the PluginConfig layer, didn't rename all UISchema / UiSchema appearances in AdaptiveForm deeply. As an example, I renamed extension/src/types/uiSchema.ts to formSchema to make sure it's consistent with flowSchema, but I didn't rename those type definitions UISchema / UIOptions to avoid too much semantic changes in AdaptiveForm.

Task Item

Screenshots

@yeze322 yeze322 changed the title chore: rename 'uiSchema' in PluginConfig to 'formSchema' chore: [not target master] rename 'uiSchema' in PluginConfig to 'formSchema' Apr 14, 2020
@a-b-r-o-w-n a-b-r-o-w-n merged commit ce8442e into visual/extension Apr 14, 2020
@a-b-r-o-w-n a-b-r-o-w-n deleted the visual/extension--formSchema branch April 14, 2020 15:13
cwhitten pushed a commit that referenced this pull request Apr 14, 2020
* rename 'ui:widget' field to 'widget'

* change default widget to ActionHeader

* fix visual editor demo

* simplify visual schema

* support loading widgets via reflection

* uischema -> visualSchema

* drive TypesWithoutWrapper as 'nowrap' in schema

* remove outdated files

* hoists visualSchema.types to @bfc/extension

* rename visualSchema to defaultVisualSchema

* fix demo

* consume Extension context in Visual

* declare schema as  Visual Props

* let visual editor consume plugin schema

* split visual config to widgets & schema

* implement visual plugin merge strategy

* migrate SendActivity to Lg plugin

* move styled components to external lib

* move prompts visual schema to 'prompts' plugin

* rename @visual-designer-elements to @ui-shared

* use ui-shared in LG

* fix visual widget type declaration

* add missing workspace dependency

* remove ActivityRenderer (replaced by LgWidget)

* remove unref vars

* rename: visualSchema -> flowSchema

* update config key to `visualSchema`

* chore: rename 'uiSchema' in PluginConfig to 'formSchema' (#2634)

* PluginConfig.uiSchema ->formSchema

* fix alphabetical issue in test
lei9444 pushed a commit to lei9444/BotFramework-Composer-1 that referenced this pull request Jun 15, 2021
* rename 'ui:widget' field to 'widget'

* change default widget to ActionHeader

* fix visual editor demo

* simplify visual schema

* support loading widgets via reflection

* uischema -> visualSchema

* drive TypesWithoutWrapper as 'nowrap' in schema

* remove outdated files

* hoists visualSchema.types to @bfc/extension

* rename visualSchema to defaultVisualSchema

* fix demo

* consume Extension context in Visual

* declare schema as  Visual Props

* let visual editor consume plugin schema

* split visual config to widgets & schema

* implement visual plugin merge strategy

* migrate SendActivity to Lg plugin

* move styled components to external lib

* move prompts visual schema to 'prompts' plugin

* rename @visual-designer-elements to @ui-shared

* use ui-shared in LG

* fix visual widget type declaration

* add missing workspace dependency

* remove ActivityRenderer (replaced by LgWidget)

* remove unref vars

* rename: visualSchema -> flowSchema

* update config key to `visualSchema`

* chore: rename 'uiSchema' in PluginConfig to 'formSchema' (microsoft#2634)

* PluginConfig.uiSchema ->formSchema

* fix alphabetical issue in test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants