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

feature: Adding VA template custom creation UI #4176

Merged
merged 38 commits into from
Oct 13, 2020
Merged

Conversation

pavolum
Copy link
Contributor

@pavolum pavolum commented Sep 18, 2020

Description

This PR consists of the custom creation UI portion of the VA template (template code in PR #4140 ). fixes #4142.

Feature break down:

  • Moved DialogWrapper component outside of client workspace and into ui-shared workspace for cross workspace reuse
  • Added virtual-assistant-creation workspace which is referenced from Client workspace and stores custom creation UI for va-core template
    • VA creation workspace is grouped with existing UI-Plugin extensions and follows same build steps
  • Altered client creation flow to call virtual-assistant-creation workspace components when user select the va-core template
  • Created ShellAPI entries for virtual-assistant-creation extension
  • Put VA Creation UI behind env variable feature flag

GeoffCoxMSFT
GeoffCoxMSFT previously approved these changes Oct 8, 2020
Base automatically changed from pavolum/va-template to main October 12, 2020 17:03
@cwhitten cwhitten dismissed GeoffCoxMSFT’s stale review October 12, 2020 17:03

The base branch was changed.

@pavolum pavolum requested a review from hatpick October 13, 2020 17:45
@pavolum pavolum merged commit 18d66bd into main Oct 13, 2020
@pavolum pavolum deleted the pavolum/va-creation-ui branch October 13, 2020 17:48
@cwhitten cwhitten mentioned this pull request Nov 13, 2020
lei9444 pushed a commit to lei9444/BotFramework-Composer-1 that referenced this pull request Jun 15, 2021
* Adding va core template plug in with corresponding plugin build steps

* Adding env variable feature flag around VA=Core template

* removing unused code that was initially added for custom runtime which has been removed

* Added creation UI workspace which is linked to and referenced from client package creation flow, Moved some UI assets to shared UI lib for cross workspace reuse, added creation UI experience for va-core template

* Minor styling changes

* Cleaning up code for review:
Moved to standard styling practices,
normalized file content structure,
added formatMessage() to UI strings,
misc clean up

* Cleaning up unused changes

* removing bot type tile

* removing bot type tile

* Making requested PR changes, general clean up, conversion of interfaces to types, adding error catching

* Converting props types to intersaction with reach router, adding await back to createProject function

* Fixing files to follow repoo linting rules

* Changed post creation logic to execute on useEffect as opposed to reliance on await

* resolve reentry bug

* removing unused function

* Fixing linting errors

* resolve reentry bug

* Fixing reference

* Updating react version in creation extension

* Updating react version in creation extension

* Making PR changes

* Fixed non static formatMessage calls

* minor syntax refactoring

* Refactoring state management for more modular state.
Implemented local state relationship to prevent excessive rerenders

* Making additional state management changes for better readability and performance.
minor clean up of interface and file names

* Fixing file naming

* Formatting template strings for localization

* changing ReachRouter version dpendency to match client reach/router version

* update Azure Publish yarn.lock

* Updating reach router version and tamplate name

Co-authored-by: Patrick Volum <pavolum@microsoft.com>
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.

Add VA template behind feature flag in Composer
8 participants