Skip to content

Commit

Permalink
Components GA release (#393)
Browse files Browse the repository at this point in the history
* Latest published -> Develop (#349)

* Release/22102020 (#332)

* Added MessageBird Whatsapp Adapter with MessageBird C# SDK (#316)

* Added MessageBird Whatsapp Adapter with MessageBird C# SDK

* Fixed README

* removed comments

* Update Bot.Builder.Community.sln

Co-authored-by: Gary Pretty <[email protected]>

* Added Infobip SMS channel (#327)

* added sms channel and code refactoring

* upgraded version of adapter

* namespace fix

* ACS SMS Adapter (#331)

* New ACS SMS Adapter

* Move ACS core library into correct location. Add readme for ACS adapter.

Co-authored-by: ahmetkocadogan <[email protected]>
Co-authored-by: ivanursic-infobip <[email protected]>

* Update README.md

* Release - 4th December 2020 (#348)

* Added MessageBird Whatsapp Adapter with MessageBird C# SDK (#316)

* Added MessageBird Whatsapp Adapter with MessageBird C# SDK

* Fixed README

* removed comments

* Update Bot.Builder.Community.sln

Co-authored-by: Gary Pretty <[email protected]>

* Added Infobip SMS channel (#327)

* added sms channel and code refactoring

* upgraded version of adapter

* namespace fix

* ACS SMS Adapter (#331)

* New ACS SMS Adapter

* Move ACS core library into correct location. Add readme for ACS adapter.

* Update README.md

* Update ACS sample to use NuGet package

* Update README.md

* Enabled Account Creation flag to true as Google's new setting does not let you deploy without OAuth credentials (#326)

Co-authored-by: Gary Pretty <[email protected]>

* Refactor infobip whatsapp sms adapter (#329)

* removed old Infobip projects

* added core project for infobip projects

* added sms adapter

* added tests for sms adapter

* added whatsapp adapter

* added tests for infobip whatsapp

* updated readme file

* added viber adapter

* infobip viber adapter added to readm file

* added Version="$(Bot_Builder_Version)" for Microsoft.Bot packages

* routes made unique

* modified accesors for adapter options

* cancelation token set to default

Co-authored-by: Gary Pretty <[email protected]>

* Update README.md (#341)

Correcting README.md formatting

* Updated readme and added MessageBird WhatsApp Adapter sample project (#333)

* fix readme add messagebird to adapter info

* fix nuget link

* added messagebird adapter sample

Co-authored-by: Gary Pretty <[email protected]>

* TextRecognizer Middleware has added (#306)

Co-authored-by: Gary Pretty <[email protected]>

* Google - Allow suggestion chips with lists / carousels (#346)

* Update ACS sample to use NuGet package

* Enable suggestion chips with lists / carousels.

* Fix merge error

* Remove redundant files

* Remove redundant files from tests folder

Co-authored-by: ahmetkocadogan <[email protected]>
Co-authored-by: ivanursic-infobip <[email protected]>
Co-authored-by: Arafat Tehsin <[email protected]>
Co-authored-by: Amine CHAFAI <[email protected]>
Co-authored-by: Vinoth Rajendran <[email protected]>

Co-authored-by: ahmetkocadogan <[email protected]>
Co-authored-by: ivanursic-infobip <[email protected]>
Co-authored-by: Arafat Tehsin <[email protected]>
Co-authored-by: Amine CHAFAI <[email protected]>
Co-authored-by: Vinoth Rajendran <[email protected]>

* Feature/cards (#284)

* Initial commit - translator and disabler

* Introduce CardUpdater/CardSet

* Combine CardDisabler and CardFocuser into CardManager

* Introduce RecursiveIdCollection

* Introduce tree/node recursion

* Replace extension chains with recursion

* Adapt card actions for channels

* Introduce payload matching

* Rename Nodes to Management/Tree

* Refactor payload matching to use parent lookups

* Work on adapting incoming card payloads (in progress)

* Finish adapting incoming card payloads

* Work on deleting actions/cards/activities (in progress)

* Convert outgoing Adaptive Cards to JObject instances

* Continue work on card deletion (in progress)

* Finish deletion functionality

* Move payload ID classes to management folder

* Create management extensions tests

* Rename PayloadId to PayloadItem

* Rename PayloadId to PayloadItem in the code

* Write test for adapting outgoing card actions

* Write test for adapting incoming payloads

* Improve AdaptOutgoingCardActions test

* Make JSON operations case-sensitive

* Keep Adaptive Card references from breaking during recursion (sometimes)

* Create card manager tests

* Rework card tree to not need a TreeNodeType enum

* Revert "Rework card tree to not need a TreeNodeType enum"

This reverts commit df3436a.

* Rework CardTree.ApplyIds to use CardTree.Recurse

* Make new child-calling lambda async and remove unneeded Recurse overload

* Create README.md

* Make the card tree recurse synchronously

* Make translation methods generic

* Make ToJObjectAndBack synchronous

* Allow ApplyIdsToBatch to accept null options

* Have GetIncomingPayload check if the activity is a message

* Introduce TrackingStyle enum

* Tweak CardManagerMiddleware.OnTurnAsync to not get the incoming payload unless tracking or deletion is enabled

* Perform a huge rename from "payload" to "action data"

I had been using "payload" to refer to the object that gets put inside a card action for it to be sent back to the bot when the user clicks the button, when it then becomes an "incoming payload." I decided this was ambiguous because "payload" normally refers to the entire body/content of an HTTP request, and so the real payloads exchanged between a bot and a channel always contain more than just what I've been calling a payload. The word payload is also used as a property of the channel data in an activity that's formed from an interactive message from Slack, and it contains what looks like the whole body of the request the Slack connector received from Slack rather than just the value of the card action

The term "action data" is much better. I've shortened it to just "data" in most cases so that it's even shorter than "payload," and that term is already used in Adaptive Cards. It's intuitively clear that "action data" and "data" refer to the same thing when seeing them used interchangeably

* Split card constants into separate files so they can be referenced more intuitively

* Create DataId class that derives from DataItem

* Document DataId and DataItem and rework their internals so that DataId only has two backing fields instead of three

* Rework SaveActivitiesAsync to not call CleanSavedActivitiesAsync

* Move non-constant DataIdTypes members to DataId

* Make CardManager.GetStateAsync public

* Create CardManager.UnsaveActivityAsync

* Add OnUpdateActivity and OnDeleteActivity to CardManagerMiddleware

* Modify OnUpdateActivity to always save the activity if it was already saved, and OnDeleteActivity to not check if ActivityId is null

* Reintroduce CardManagerTurnState in order to allow the card manager to bypass the middleware when updating and deleting activities

* Have UnsaveActivityAsync remove all activities with a matching ID instead of just one

* Remove CleanSavedActivitiesAsync from DeleteAsync

* Remove CleanSavedActivitiesAsync

* Rename DeleteAsync to DeleteActionSourceAsync

* Make DataId.Types a ReadOnlyCollection property instead of an IList

* Change default middleware options from properties to methods

* Call ClearTrackedIdsAsync even when none of the activities have attachments

* Change ChannelsWithMessageUpdates to an instance property

* Start creating CardManagerMiddlewareTests

* Experiment with ways to test the card manager middleware

* Create another version of ChannelsWithMessageUpdates_CanBeChanged, this time using a new TestFlow extension method

* Write tests for middleware options

* Have MiddlewareIgnoreUpdate use activities instead of strings

* Update to Bot Builder 4.9

* Add OnUpdateActivity and OnDeleteActivity tests

* Add cards projects back to solution

* Remove superfluous middleware tests

* Switch to inline lambda callbacks in middleware tests

* Move ChannelData.cs to Management folder

* Add fluent setters for middleware options

* Make DataId.Types public

* Correct references in doc comments

* Give DataIdOptions.Set a fluent interface and remove some unused methods

* Create Cards Library Sample

* Add anonymous types to management extensions tests

* Make applying ID's work with non-object non-enumerable types

* Add TODO comment

* Remove second comma from appsettings.json

* Set AutoClearEnabledOnSend to false

* Remove unnecessary null coalescing operator in GetNotNullAsync

* Use SetAsync to account for state that has potentially been copied from a JObject

* Change IMessageActivity to Activity in card manager state to make deserialization easier

* Rework card manager middleware to only use ID options for applying ID's and not for enabling/disabling them

* Clean up card manager middleware tests

* Improve cards library bot messages

* Have sample reference debug build of cards library

* Fix card manager middleware to work if the incoming action has no ID's

* Fix missing parentheses

* Move cards management tests to their own namespace

* Remove delegates from Adaptive Card translator settings

* Fix exceptions in AdaptiveCardTranslator

* Remove usings in AdaptiveCardTranslatorSettings

* Implement MicrosoftTranslatorConfig

* Remove extraneous null checks in AdaptiveCardTranslator

* Make "value" configurable in PropertiesToTranslate

* Expand use of string constants for Adaptive Cards

* Touch up Adaptive Card translator

* Create Adaptive Card translator tests

* Modify card sample text

* Give translator subscription key a public getter

* Make sure actions with no data ID's are enabled

* Add TODO comments

* Implement Adaptive Card translation sample

* Fix null reference bug in cards sample

* Don't use translator endpoint if it's white space

* Add translator config to cards sample appsettings.json

* Adjust cards library sample to use behavior constants and better method names, and to inject a card manager

* Rename DataIdTypes to DataIdScopes

* Propagate type/scope rename to sample

* Remove unnecessary usings from cards library

* Fix missed name change in DataId

* Implement _cardsLibrary action data property as a wrapper for all cards library data (currently just action data ID's)

* Make DataItem generic and revert to having DataId derive from it

* Update the sample to use the word "deactivate" as an umbrella term for disabling and deleting

* Create way to set values in library data

* Provide a choice between merging library data and replacing it

* Fix CardTree.SetLibraryData to use merge parameter

* Allow for null data in SetLibraryData

* Update NuGet packages for tests

* Create SetLibraryDataTests

* Change SetLibraryData to SetActionBehavior

* Introduce in-action behaviors

* Rework auto-deactivate behavior to use a string instead of a nullable bool

* Expose methods to set behaviors on many tree nodes instead of just batches

* Expose methods to set data ID's for many tree nodes instead of just batches

* Rename SetFor to SetIn

* Require explicit node types for the card tree instead of resolving types at runtime

* Apply ID's at the library data node instead of the action data node

* Write data ID tests

* Remove unused members in DataIdTests

* Write action behavior tests

* Create failing test for card tree parallel-route bug

* Fix card tree parallel-route bug in two ways

1. Check if the child caller is null
2. Short-circuit recursion when the exit node has been passed

* Create preserve-values sample

* Start working on cards library readme

* Finish disable-and-delete section of cards library readme

* Update Bot.Builder.Community.sln

Fix bad merge in sln file.

* Update SLN file and amend cards project file to use shared Bot Builder version

* Further sln update to fix build error.

* Add shared targets import to Cards project

Co-authored-by: Kyle Delaney <[email protected]>
Co-authored-by: Kyle Delaney <[email protected]>
Co-authored-by: TharosTheDragon <[email protected]>
Co-authored-by: Gary Pretty <[email protected]>

* Update to SDK 4.11.1

* Add translation section to cards library readme (#356)

* Initial commit - translator and disabler

* Introduce CardUpdater/CardSet

* Combine CardDisabler and CardFocuser into CardManager

* Introduce RecursiveIdCollection

* Introduce tree/node recursion

* Replace extension chains with recursion

* Adapt card actions for channels

* Introduce payload matching

* Rename Nodes to Management/Tree

* Refactor payload matching to use parent lookups

* Work on adapting incoming card payloads (in progress)

* Finish adapting incoming card payloads

* Work on deleting actions/cards/activities (in progress)

* Convert outgoing Adaptive Cards to JObject instances

* Continue work on card deletion (in progress)

* Finish deletion functionality

* Move payload ID classes to management folder

* Create management extensions tests

* Rename PayloadId to PayloadItem

* Rename PayloadId to PayloadItem in the code

* Write test for adapting outgoing card actions

* Write test for adapting incoming payloads

* Improve AdaptOutgoingCardActions test

* Make JSON operations case-sensitive

* Keep Adaptive Card references from breaking during recursion (sometimes)

* Create card manager tests

* Rework card tree to not need a TreeNodeType enum

* Revert "Rework card tree to not need a TreeNodeType enum"

This reverts commit df3436a.

* Rework CardTree.ApplyIds to use CardTree.Recurse

* Make new child-calling lambda async and remove unneeded Recurse overload

* Create README.md

* Make the card tree recurse synchronously

* Make translation methods generic

* Make ToJObjectAndBack synchronous

* Allow ApplyIdsToBatch to accept null options

* Have GetIncomingPayload check if the activity is a message

* Introduce TrackingStyle enum

* Tweak CardManagerMiddleware.OnTurnAsync to not get the incoming payload unless tracking or deletion is enabled

* Perform a huge rename from "payload" to "action data"

I had been using "payload" to refer to the object that gets put inside a card action for it to be sent back to the bot when the user clicks the button, when it then becomes an "incoming payload." I decided this was ambiguous because "payload" normally refers to the entire body/content of an HTTP request, and so the real payloads exchanged between a bot and a channel always contain more than just what I've been calling a payload. The word payload is also used as a property of the channel data in an activity that's formed from an interactive message from Slack, and it contains what looks like the whole body of the request the Slack connector received from Slack rather than just the value of the card action

The term "action data" is much better. I've shortened it to just "data" in most cases so that it's even shorter than "payload," and that term is already used in Adaptive Cards. It's intuitively clear that "action data" and "data" refer to the same thing when seeing them used interchangeably

* Split card constants into separate files so they can be referenced more intuitively

* Create DataId class that derives from DataItem

* Document DataId and DataItem and rework their internals so that DataId only has two backing fields instead of three

* Rework SaveActivitiesAsync to not call CleanSavedActivitiesAsync

* Move non-constant DataIdTypes members to DataId

* Make CardManager.GetStateAsync public

* Create CardManager.UnsaveActivityAsync

* Add OnUpdateActivity and OnDeleteActivity to CardManagerMiddleware

* Modify OnUpdateActivity to always save the activity if it was already saved, and OnDeleteActivity to not check if ActivityId is null

* Reintroduce CardManagerTurnState in order to allow the card manager to bypass the middleware when updating and deleting activities

* Have UnsaveActivityAsync remove all activities with a matching ID instead of just one

* Remove CleanSavedActivitiesAsync from DeleteAsync

* Remove CleanSavedActivitiesAsync

* Rename DeleteAsync to DeleteActionSourceAsync

* Make DataId.Types a ReadOnlyCollection property instead of an IList

* Change default middleware options from properties to methods

* Call ClearTrackedIdsAsync even when none of the activities have attachments

* Change ChannelsWithMessageUpdates to an instance property

* Start creating CardManagerMiddlewareTests

* Experiment with ways to test the card manager middleware

* Create another version of ChannelsWithMessageUpdates_CanBeChanged, this time using a new TestFlow extension method

* Write tests for middleware options

* Have MiddlewareIgnoreUpdate use activities instead of strings

* Update to Bot Builder 4.9

* Add OnUpdateActivity and OnDeleteActivity tests

* Add cards projects back to solution

* Remove superfluous middleware tests

* Switch to inline lambda callbacks in middleware tests

* Move ChannelData.cs to Management folder

* Add fluent setters for middleware options

* Make DataId.Types public

* Correct references in doc comments

* Give DataIdOptions.Set a fluent interface and remove some unused methods

* Create Cards Library Sample

* Add anonymous types to management extensions tests

* Make applying ID's work with non-object non-enumerable types

* Add TODO comment

* Remove second comma from appsettings.json

* Set AutoClearEnabledOnSend to false

* Remove unnecessary null coalescing operator in GetNotNullAsync

* Use SetAsync to account for state that has potentially been copied from a JObject

* Change IMessageActivity to Activity in card manager state to make deserialization easier

* Rework card manager middleware to only use ID options for applying ID's and not for enabling/disabling them

* Clean up card manager middleware tests

* Improve cards library bot messages

* Have sample reference debug build of cards library

* Fix card manager middleware to work if the incoming action has no ID's

* Fix missing parentheses

* Move cards management tests to their own namespace

* Remove delegates from Adaptive Card translator settings

* Fix exceptions in AdaptiveCardTranslator

* Remove usings in AdaptiveCardTranslatorSettings

* Implement MicrosoftTranslatorConfig

* Remove extraneous null checks in AdaptiveCardTranslator

* Make "value" configurable in PropertiesToTranslate

* Expand use of string constants for Adaptive Cards

* Touch up Adaptive Card translator

* Create Adaptive Card translator tests

* Modify card sample text

* Give translator subscription key a public getter

* Make sure actions with no data ID's are enabled

* Add TODO comments

* Implement Adaptive Card translation sample

* Fix null reference bug in cards sample

* Don't use translator endpoint if it's white space

* Add translator config to cards sample appsettings.json

* Adjust cards library sample to use behavior constants and better method names, and to inject a card manager

* Rename DataIdTypes to DataIdScopes

* Propagate type/scope rename to sample

* Remove unnecessary usings from cards library

* Fix missed name change in DataId

* Implement _cardsLibrary action data property as a wrapper for all cards library data (currently just action data ID's)

* Make DataItem generic and revert to having DataId derive from it

* Update the sample to use the word "deactivate" as an umbrella term for disabling and deleting

* Create way to set values in library data

* Provide a choice between merging library data and replacing it

* Fix CardTree.SetLibraryData to use merge parameter

* Allow for null data in SetLibraryData

* Update NuGet packages for tests

* Create SetLibraryDataTests

* Change SetLibraryData to SetActionBehavior

* Introduce in-action behaviors

* Rework auto-deactivate behavior to use a string instead of a nullable bool

* Expose methods to set behaviors on many tree nodes instead of just batches

* Expose methods to set data ID's for many tree nodes instead of just batches

* Rename SetFor to SetIn

* Require explicit node types for the card tree instead of resolving types at runtime

* Apply ID's at the library data node instead of the action data node

* Write data ID tests

* Remove unused members in DataIdTests

* Write action behavior tests

* Create failing test for card tree parallel-route bug

* Fix card tree parallel-route bug in two ways

1. Check if the child caller is null
2. Short-circuit recursion when the exit node has been passed

* Create preserve-values sample

* Start working on cards library readme

* Finish disable-and-delete section of cards library readme

* Start writing PreserveValues section of readme

* Remove PreserveValues functionality from library

An update to Teams has rendered this functionality unnecessary

* Update Bot.Builder.Community.sln

Fix bad merge in sln file.

* Update SLN file and amend cards project file to use shared Bot Builder version

* Further sln update to fix build error.

* Add shared targets import to Cards project

* Have TranslateManyDelegate use IEnumerable

* Add translation section to readme

Co-authored-by: Kyle Delaney <[email protected]>
Co-authored-by: Kyle Delaney <[email protected]>
Co-authored-by: TharosTheDragon <[email protected]>
Co-authored-by: Gary Pretty <[email protected]>

* Fixed link to sample (#355)

* Custom action EmailInput to bot framework composer (#353)

* Updated Bot.Builder.Community.Adapters.MessageBird.csproj (#351)

Updated Bot.Builder.Community.Adapters.MessageBird.csproj file, added Description for NuGet package.

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Change json to jsonc in cards library readme (#367)

* Add translation section to cards library readme (#356)

* Initial commit - translator and disabler

* Introduce CardUpdater/CardSet

* Combine CardDisabler and CardFocuser into CardManager

* Introduce RecursiveIdCollection

* Introduce tree/node recursion

* Replace extension chains with recursion

* Adapt card actions for channels

* Introduce payload matching

* Rename Nodes to Management/Tree

* Refactor payload matching to use parent lookups

* Work on adapting incoming card payloads (in progress)

* Finish adapting incoming card payloads

* Work on deleting actions/cards/activities (in progress)

* Convert outgoing Adaptive Cards to JObject instances

* Continue work on card deletion (in progress)

* Finish deletion functionality

* Move payload ID classes to management folder

* Create management extensions tests

* Rename PayloadId to PayloadItem

* Rename PayloadId to PayloadItem in the code

* Write test for adapting outgoing card actions

* Write test for adapting incoming payloads

* Improve AdaptOutgoingCardActions test

* Make JSON operations case-sensitive

* Keep Adaptive Card references from breaking during recursion (sometimes)

* Create card manager tests

* Rework card tree to not need a TreeNodeType enum

* Revert "Rework card tree to not need a TreeNodeType enum"

This reverts commit df3436a.

* Rework CardTree.ApplyIds to use CardTree.Recurse

* Make new child-calling lambda async and remove unneeded Recurse overload

* Create README.md

* Make the card tree recurse synchronously

* Make translation methods generic

* Make ToJObjectAndBack synchronous

* Allow ApplyIdsToBatch to accept null options

* Have GetIncomingPayload check if the activity is a message

* Introduce TrackingStyle enum

* Tweak CardManagerMiddleware.OnTurnAsync to not get the incoming payload unless tracking or deletion is enabled

* Perform a huge rename from "payload" to "action data"

I had been using "payload" to refer to the object that gets put inside a card action for it to be sent back to the bot when the user clicks the button, when it then becomes an "incoming payload." I decided this was ambiguous because "payload" normally refers to the entire body/content of an HTTP request, and so the real payloads exchanged between a bot and a channel always contain more than just what I've been calling a payload. The word payload is also used as a property of the channel data in an activity that's formed from an interactive message from Slack, and it contains what looks like the whole body of the request the Slack connector received from Slack rather than just the value of the card action

The term "action data" is much better. I've shortened it to just "data" in most cases so that it's even shorter than "payload," and that term is already used in Adaptive Cards. It's intuitively clear that "action data" and "data" refer to the same thing when seeing them used interchangeably

* Split card constants into separate files so they can be referenced more intuitively

* Create DataId class that derives from DataItem

* Document DataId and DataItem and rework their internals so that DataId only has two backing fields instead of three

* Rework SaveActivitiesAsync to not call CleanSavedActivitiesAsync

* Move non-constant DataIdTypes members to DataId

* Make CardManager.GetStateAsync public

* Create CardManager.UnsaveActivityAsync

* Add OnUpdateActivity and OnDeleteActivity to CardManagerMiddleware

* Modify OnUpdateActivity to always save the activity if it was already saved, and OnDeleteActivity to not check if ActivityId is null

* Reintroduce CardManagerTurnState in order to allow the card manager to bypass the middleware when updating and deleting activities

* Have UnsaveActivityAsync remove all activities with a matching ID instead of just one

* Remove CleanSavedActivitiesAsync from DeleteAsync

* Remove CleanSavedActivitiesAsync

* Rename DeleteAsync to DeleteActionSourceAsync

* Make DataId.Types a ReadOnlyCollection property instead of an IList

* Change default middleware options from properties to methods

* Call ClearTrackedIdsAsync even when none of the activities have attachments

* Change ChannelsWithMessageUpdates to an instance property

* Start creating CardManagerMiddlewareTests

* Experiment with ways to test the card manager middleware

* Create another version of ChannelsWithMessageUpdates_CanBeChanged, this time using a new TestFlow extension method

* Write tests for middleware options

* Have MiddlewareIgnoreUpdate use activities instead of strings

* Update to Bot Builder 4.9

* Add OnUpdateActivity and OnDeleteActivity tests

* Add cards projects back to solution

* Remove superfluous middleware tests

* Switch to inline lambda callbacks in middleware tests

* Move ChannelData.cs to Management folder

* Add fluent setters for middleware options

* Make DataId.Types public

* Correct references in doc comments

* Give DataIdOptions.Set a fluent interface and remove some unused methods

* Create Cards Library Sample

* Add anonymous types to management extensions tests

* Make applying ID's work with non-object non-enumerable types

* Add TODO comment

* Remove second comma from appsettings.json

* Set AutoClearEnabledOnSend to false

* Remove unnecessary null coalescing operator in GetNotNullAsync

* Use SetAsync to account for state that has potentially been copied from a JObject

* Change IMessageActivity to Activity in card manager state to make deserialization easier

* Rework card manager middleware to only use ID options for applying ID's and not for enabling/disabling them

* Clean up card manager middleware tests

* Improve cards library bot messages

* Have sample reference debug build of cards library

* Fix card manager middleware to work if the incoming action has no ID's

* Fix missing parentheses

* Move cards management tests to their own namespace

* Remove delegates from Adaptive Card translator settings

* Fix exceptions in AdaptiveCardTranslator

* Remove usings in AdaptiveCardTranslatorSettings

* Implement MicrosoftTranslatorConfig

* Remove extraneous null checks in AdaptiveCardTranslator

* Make "value" configurable in PropertiesToTranslate

* Expand use of string constants for Adaptive Cards

* Touch up Adaptive Card translator

* Create Adaptive Card translator tests

* Modify card sample text

* Give translator subscription key a public getter

* Make sure actions with no data ID's are enabled

* Add TODO comments

* Implement Adaptive Card translation sample

* Fix null reference bug in cards sample

* Don't use translator endpoint if it's white space

* Add translator config to cards sample appsettings.json

* Adjust cards library sample to use behavior constants and better method names, and to inject a card manager

* Rename DataIdTypes to DataIdScopes

* Propagate type/scope rename to sample

* Remove unnecessary usings from cards library

* Fix missed name change in DataId

* Implement _cardsLibrary action data property as a wrapper for all cards library data (currently just action data ID's)

* Make DataItem generic and revert to having DataId derive from it

* Update the sample to use the word "deactivate" as an umbrella term for disabling and deleting

* Create way to set values in library data

* Provide a choice between merging library data and replacing it

* Fix CardTree.SetLibraryData to use merge parameter

* Allow for null data in SetLibraryData

* Update NuGet packages for tests

* Create SetLibraryDataTests

* Change SetLibraryData to SetActionBehavior

* Introduce in-action behaviors

* Rework auto-deactivate behavior to use a string instead of a nullable bool

* Expose methods to set behaviors on many tree nodes instead of just batches

* Expose methods to set data ID's for many tree nodes instead of just batches

* Rename SetFor to SetIn

* Require explicit node types for the card tree instead of resolving types at runtime

* Apply ID's at the library data node instead of the action data node

* Write data ID tests

* Remove unused members in DataIdTests

* Write action behavior tests

* Create failing test for card tree parallel-route bug

* Fix card tree parallel-route bug in two ways

1. Check if the child caller is null
2. Short-circuit recursion when the exit node has been passed

* Create preserve-values sample

* Start working on cards library readme

* Finish disable-and-delete section of cards library readme

* Start writing PreserveValues section of readme

* Remove PreserveValues functionality from library

An update to Teams has rendered this functionality unnecessary

* Update Bot.Builder.Community.sln

Fix bad merge in sln file.

* Update SLN file and amend cards project file to use shared Bot Builder version

* Further sln update to fix build error.

* Add shared targets import to Cards project

* Have TranslateManyDelegate use IEnumerable

* Add translation section to readme

Co-authored-by: Kyle Delaney <[email protected]>
Co-authored-by: Kyle Delaney <[email protected]>
Co-authored-by: TharosTheDragon <[email protected]>
Co-authored-by: Gary Pretty <[email protected]>

* Fixed link to sample (#355)

* Custom action EmailInput to bot framework composer (#353)

* Updated Bot.Builder.Community.Adapters.MessageBird.csproj (#351)

Updated Bot.Builder.Community.Adapters.MessageBird.csproj file, added Description for NuGet package.

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Change json to jsonc in cards library readme (#367)

* Update SDK to 4.12 (#371)

* Fix links to samples (#374)

* chore: update the SentimentAnalyzer reference for Sentiment Analysis Middleware (#375)

Co-authored-by: Gary Pretty <[email protected]>

* Merge Packages Preview Branch into Develop to prep for GA release (#389)

* New CallDialogs component for composer (#365)

* Added CallDialogs component

* Updated nuget package and sample

* Implemented call dialogs sample

* Updated sample to use 1.3-preview package of call dialogs

* Added readme

* Added screen shots

* Update readme.md

* Update readme.md

* Update AllowedCallersClaimsValidator.cs

Removed copyright header

* Stevenic/storage component (#368)

* Added CallDialogs component

* Updated nuget package and sample

* Implemented call dialogs sample

* Updated sample to use 1.3-preview package of call dialogs

* Added readme

* Added screen shots

* Update readme.md

* Update readme.md

* Added new storage component

* Added Storage Sample

* Updated readme for storage component

* Update readme.md

Fixed typo

* Update AllowedCallersClaimsValidator.cs

* Update AllowedCallersClaimsValidationTests.cs

* Update MessagesTrigger.cs

* Update ActivitySerializationSettings.cs

* Update SkillsTrigger.cs

* Update Startup.cs

* Update BotController.cs

* Update SkillController.cs

* Update Program.cs

* Update Startup.cs

* Update ComposerBot.cs

* Update ComposerBotPathExtensions.cs

* Update ComposerSettingsExtensions.cs

* Update LuisConfig.cs

* Update BlobStorageConfiguration.cs

* Update BotFeatureSettings.cs

* Update BotSettings.cs

* Update BotSkillConfiguration.cs

* Update SkillConversationIdFactory.cs

* Update MultiplyDialog.cs

* Update CustomActionComponentRegistration.cs

* Update ActionsTests.cs

* Update ControllingConversationTests.cs

* Adapter components: Zoom, Alexa, ActionsSDK and ACS SMS (#373)

* Adapter components: Zoom, Alexa, ActionsSDK and ACS SMS

* Adapters: add data annotation validations for adapter component

* Components: Add new tag msbot-component and category tags (#377)

* Components: upgrade to 4.13rc2, update to BotComponent base class, rename adapter schemas, add adapter type (#379)

* GetWeather delcarative package added to packages-preview feature branch

* Update Adapter Component project files to supress NU5104 temporarily and add PackageIcon property.

* Add nuget.config to add Bot Builder MyGet as a package source

* Update GetWeather dialog project to align with other projects in the solution.

* Temporarily removed the Adaptive Dialog Test project to allow for build / publish of preview packages.

* Update README.md

* Update README.md

* Update project URLs to correct Component library locations.

* Add LivePerson Handoff Package and Handoff Shared package

* Update shared targets to rc5. Fix runtime reference in handoff package.

* Update LivePerson controller to handle RichContentEvents

* Update SDK version shared target to 4.13.0

* Updated shared handoff proj properties

* Add readme for LivePerson handoff

* Update README.md

* ADapter schemas: add type, update doc link to main repo (#382)

* A collection of custom input for Bot Framework Composer (#381)

* Update tag for LivePerson package

* ServiceNow Handoff Implementation (#388)

* Add LivePerson handoff component. Tidy up package references and shared NuGet props.

* Update SDK / preview targets

* First implementation of ServiceNow handoff utilising a fixed user/password for demonstration purposes. Further work is identified to identify pass-through authentication (SSO)

* adding oauth config setting and trace

* oauth work

* oAuth implementation and readme

* new response handling

Co-authored-by: Gary Pretty <[email protected]>

* Alexa component help link issue has been fixed (#383)

* Alexa helplink issue has been fixed

* Alexa components help link has fixec

* Stevenic develop (#391)

* Added CallDialogs component

* Updated nuget package and sample

* Implemented call dialogs sample

* Updated sample to use 1.3-preview package of call dialogs

* Added readme

* Added screen shots

* Update readme.md

* Update readme.md

* Update AllowedCallersClaimsValidator.cs

Removed copyright header

* Fix links to samples (#374)

* chore: update the SentimentAnalyzer reference for Sentiment Analysis Middleware (#375)

Co-authored-by: Gary Pretty <[email protected]>

Co-authored-by: Kyle Delaney <[email protected]>
Co-authored-by: Arafat Tehsin <[email protected]>
Co-authored-by: Gary Pretty <[email protected]>

* Add sso token exchange skill handler package (#387)

* Add Bot.Builder.Community.Components.TokenExchangeSkillHandler

* Remove package generation from TokenExchangeSkillHandler project

* Readme fix

* Bot.Builder.Community.Components.TokenExchangeSkillHandler readme update

* Add Prerequisite to readme

* Add null checks to SkillsConfiguration

* Add SkillConfigurationTests

Co-authored-by: Steven Ickman <[email protected]>
Co-authored-by: Carlos Castro <[email protected]>
Co-authored-by: Stephan Bisser <[email protected]>
Co-authored-by: Vinoth Rajendran <[email protected]>
Co-authored-by: Darren Jefford <[email protected]>
Co-authored-by: Kyle Delaney <[email protected]>
Co-authored-by: Arafat Tehsin <[email protected]>
Co-authored-by: Eric Dahlvang <[email protected]>

* Component GA readme updates (#392)

* Update root readme adding Components and fix up GetWeather package to include declarative assets in correct package location.

* Update readmes

* Update readmes

* Update shared targets to 4.13.1 for SDK

Co-authored-by: ahmetkocadogan <[email protected]>
Co-authored-by: ivanursic-infobip <[email protected]>
Co-authored-by: Arafat Tehsin <[email protected]>
Co-authored-by: Amine CHAFAI <[email protected]>
Co-authored-by: Vinoth Rajendran <[email protected]>
Co-authored-by: Kyle Delaney <[email protected]>
Co-authored-by: Kyle Delaney <[email protected]>
Co-authored-by: Kyle Delaney <[email protected]>
Co-authored-by: TharosTheDragon <[email protected]>
Co-authored-by: Artur Laksberg <[email protected]>
Co-authored-by: Steven Ickman <[email protected]>
Co-authored-by: Carlos Castro <[email protected]>
Co-authored-by: Stephan Bisser <[email protected]>
Co-authored-by: Darren Jefford <[email protected]>
Co-authored-by: Eric Dahlvang <[email protected]>
  • Loading branch information
16 people authored May 11, 2021
1 parent 4fa4de7 commit 1349229
Show file tree
Hide file tree
Showing 383 changed files with 44,675 additions and 91 deletions.
167 changes: 156 additions & 11 deletions Bot.Builder.Community.sln

Large diffs are not rendered by default.

3 changes: 2 additions & 1 deletion CommonTargets/library.shared.targets
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
<Project>

<PropertyGroup>
<Bot_Builder_Version>4.12.1</Bot_Builder_Version>
<Bot_Builder_Version>4.13.1</Bot_Builder_Version>
<Bot_Builder_Preview_Version>4.13.0-rc5.preview</Bot_Builder_Preview_Version>
</PropertyGroup>

</Project>
2 changes: 1 addition & 1 deletion Directory.Build.props
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@
<PropertyGroup>
<!-- Rules found at: https://aka.ms/Microsoft-NuGet-Compliance -->
<PackageProjectUrl>http://www.github.com/botbuildercommunity/botbuildercommunity-dotnet</PackageProjectUrl>
<PackageIconUrl>https://bot-framework.azureedge.net/static/58168-ae253ca613/intercom-webui/v1.6.2/assets/landing-page/images/BotFrame_Logo_Icon.png</PackageIconUrl>
<IconUrl>https://bot-framework.azureedge.net/static/58168-ae253ca613/intercom-webui/v1.6.2/assets/landing-page/images/BotFrame_Logo_Icon.png</IconUrl>
<PackageLicenseUrl>http://www.github.com/botbuildercommunity/botbuildercommunity-dotnet/blob/master/LICENSE</PackageLicenseUrl>
<PackageRequireLicenseAcceptance>true</PackageRequireLicenseAcceptance>
<RepositoryUrl>
Expand Down
2 changes: 1 addition & 1 deletion LICENSE
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
MIT License

Copyright (c) 2019 Bot Builder Community
Copyright (c) 2021 Bot Builder Community

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
Expand Down
98 changes: 76 additions & 22 deletions README.md

Large diffs are not rendered by default.

Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
using Azure.Core;
using System.ComponentModel.DataAnnotations;

namespace Bot.Builder.Community.Adapters.ACS.SMS
{
Expand All @@ -7,10 +8,12 @@ namespace Bot.Builder.Community.Adapters.ACS.SMS
/// </summary>
public class AcsSmsAdapterOptions
{
[Required]
public string AcsConnectionString { get; set; }

public bool EnableDeliveryReports { get; set; } = true;

[Required]
public string AcsPhoneNumber { get; set; }

public RetryOptions RetryOptions { get; set; }
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
<Import Project="$([MSBuild]::GetDirectoryNameOfFileAbove('$(MSBuildThisFileDirectory)../', 'Bot.Builder.Community.sln'))\CommonTargets\library.shared.targets" />

<PropertyGroup>
<TargetFramework>netstandard2.0</TargetFramework>
<TargetFramework>netstandard2.0</TargetFramework>
<Description>Adapter for v4 of the Bot Builder .NET SDK to allow for a bot to be used with SMS via Azure Communication Services.</Description>
<Authors>Bot Builder Community</Authors>
<Company>Bot Builder Community</Company>
Expand All @@ -13,7 +13,7 @@
<AssemblyVersion>1.0.0</AssemblyVersion>
<RepositoryUrl>https://github.com/BotBuilderCommunity/botbuilder-community-dotnet/</RepositoryUrl>
<GeneratePackageOnBuild>false</GeneratePackageOnBuild>
</PropertyGroup>
</PropertyGroup>

<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
Expand All @@ -25,6 +25,7 @@
<PackageReference Include="Microsoft.Azure.EventGrid" Version="3.2.0" />
<PackageReference Include="Microsoft.Bot.Builder.Integration.AspNet.Core" Version="$(Bot_Builder_Version)" />
<PackageReference Include="Microsoft.SourceLink.GitHub" Version="1.0.0" PrivateAssets="All" />
<PackageReference Include="System.ComponentModel.Annotations" Version="5.0.0" />
</ItemGroup>

<ItemGroup>
Expand Down
4 changes: 2 additions & 2 deletions libraries/Bot.Builder.Community.Adapters.ACS.SMS/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@

## Description

This is part of the [Bot Builder Community Extensions](https://github.com/botbuildercommunity) project which contains various pieces of middleware, recognizers and other components for use with the Bot Builder .NET SDK v4.
This is part of the [Bot Builder Community](https://github.com/botbuildercommunity) project which contains Bot Framework Components and other projects / packages for use with Bot Framework Composer and the Bot Builder .NET SDK v4.

The Azure Communication Services SMS Adapter allows you to add an additional endpoint to your bot for SMS via Azure Communication Services. The adapter can be used
in conjunction with other channels meaning, for example, you can have a bot exposed on out of the box channels such as Facebook and
Expand All @@ -33,7 +33,7 @@ Install into your project use the following command in the package manager.

## Sample

Sample bot is available [here](https://github.com/BotBuilderCommunity/botbuilder-community-dotnet/tree/develop/samples/ACS%20SMS%20Adapter%20Sample).
Sample bot is available [here](../../samples/ACS%20SMS%20Adapter%20Sample).

## Usage

Expand Down
Original file line number Diff line number Diff line change
@@ -1,11 +1,15 @@
namespace Bot.Builder.Community.Adapters.ActionsSDK
using System.ComponentModel.DataAnnotations;

namespace Bot.Builder.Community.Adapters.ActionsSDK
{
public class ActionsSdkAdapterOptions
{
public bool ShouldEndSessionByDefault { get; set; } = true;

[Required]
public string ActionInvocationName { get; set; }

[Required]
public string ActionProjectId { get; set; }
}
}
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@

<ItemGroup>
<PackageReference Include="Microsoft.Bot.Builder.Integration.AspNet.Core" Version="$(Bot_Builder_Version)" />
<PackageReference Include="System.ComponentModel.Annotations" Version="5.0.0" />
</ItemGroup>

<ItemGroup>
Expand Down
4 changes: 2 additions & 2 deletions libraries/Bot.Builder.Community.Adapters.ActionsSDK/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@

## Description

This is part of the [Bot Builder Community Extensions](https://github.com/botbuildercommunity) project which contains various pieces of middleware, recognizers and other components for use with the Bot Builder .NET SDK v4.
This is part of the [Bot Builder Community](https://github.com/botbuildercommunity) project which contains Bot Framework Components and other projects / packages for use with Bot Framework Composer and the Bot Builder .NET SDK v4.

The Actions SDK Adapter allows you to add an additional endpoint to your bot for conversational actions built with the latest Google Actions SDK. The Google endpoint can be used in conjunction with other channels meaning, for example, you can have a bot exposed on out of the box channels such as Facebook and Teams, but also via a Google Action (as well as side by side with other adapters (e.g. the Alexa adapter) also available from the Bot Builder Community Project).

Expand All @@ -35,7 +35,7 @@ Install into your project use the following command in the package manager.

## Sample

A Sample bot with examples of Actions SDK specific functionality (such as sending cards, lists etc.) is available [here](https://github.com/BotBuilderCommunity/botbuilder-community-dotnet/samples/Actions%20SDK%20Adapter%20Sample).
A Sample bot with examples of Actions SDK specific functionality (such as sending cards, lists etc.) is available [here](../../samples/Actions%20SDK%20Adapter%20Sample).

## Usage

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@

## Description

This is part of the [Bot Builder Community Extensions](https://github.com/botbuildercommunity) project which contains various pieces of middleware, recognizers and other components for use with the Bot Builder .NET SDK v4.
This is part of the [Bot Builder Community](https://github.com/botbuildercommunity) project which contains Bot Framework Components and other projects / packages for use with Bot Framework Composer and the Bot Builder .NET SDK v4.

The Alexa Core Adapter contains the core of the schema transformation and authorization logic that powers both the [Alexa Adapter](/libraries/Bot.Builder.Community.Adapters.Alexa) and the [Bot Framework Alexa channel](https://docs.microsoft.com/en-us/azure/bot-service/bot-service-channel-connect-alexa?view=azure-bot-service-4.0).

Expand Down
Original file line number Diff line number Diff line change
@@ -1,4 +1,6 @@
namespace Bot.Builder.Community.Adapters.Alexa
using System.ComponentModel.DataAnnotations;

namespace Bot.Builder.Community.Adapters.Alexa
{
public class AlexaAdapterOptions
{
Expand All @@ -15,6 +17,7 @@ public class AlexaAdapterOptions
/// This will be used to verify requests coming from Alexa are for this bot.
/// See https://developer.amazon.com/en-US/docs/alexa/custom-skills/handle-requests-sent-by-alexa.html for more information including how to get this value.
/// </remarks>
[Required]
public string AlexaSkillId { get; set; }
}
}
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@
<ItemGroup>
<PackageReference Include="Microsoft.Bot.Builder.Integration.AspNet.Core" Version="$(Bot_Builder_Version)" />
<PackageReference Include="Microsoft.Net.Http.Headers" Version="2.1.1" />
<PackageReference Include="System.ComponentModel.Annotations" Version="5.0.0" />
</ItemGroup>

<ItemGroup>
Expand Down
4 changes: 2 additions & 2 deletions libraries/Bot.Builder.Community.Adapters.Alexa/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@

## Description

This is part of the [Bot Builder Community Extensions](https://github.com/botbuildercommunity) project which contains various pieces of middleware, recognizers and other components for use with the Bot Builder .NET SDK v4.
This is part of the [Bot Builder Community](https://github.com/botbuildercommunity) project which contains Bot Framework Components and other projects / packages for use with Bot Framework Composer and the Bot Builder .NET SDK v4.

The Alexa Adapter allows you to add an additional endpoint to your bot for Alexa Skills. The Alexa endpoint can be used
in conjunction with other channels meaning, for example, you can have a bot exposed on out of the box channels such as Facebook and
Expand Down Expand Up @@ -36,7 +36,7 @@ Install into your project use the following command in the package manager.

## Sample

Sample bot, showing examples of Alexa specific functionality is available [here](https://github.com/BotBuilderCommunity/botbuilder-community-dotnet/samples/Alexa%20Adapter%20Sample).
Sample bots showing examples of Alexa specific functionality are available [here](../../samples/Alexa%20Adapter%20Sample) and [here](../../samples/Cortana%20Assistant%20Alexa%20Sample).

## Usage

Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 2 additions & 2 deletions libraries/Bot.Builder.Community.Adapters.Google/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@

## Description

This is part of the [Bot Builder Community Extensions](https://github.com/botbuildercommunity) project which contains various pieces of middleware, recognizers and other components for use with the Bot Builder .NET SDK v4.
This is part of the [Bot Builder Community](https://github.com/botbuildercommunity) project which contains Bot Framework Components and other projects / packages for use with Bot Framework Composer and the Bot Builder .NET SDK v4.

The Google Adapter allows you to add an additional endpoint to your bot for custom Google Actions. The Google endpoint can be used
in conjunction with other channels meaning, for example, you can have a bot exposed on out of the box channels such as Facebook and
Expand Down Expand Up @@ -37,7 +37,7 @@ Install into your project use the following command in the package manager.

## Sample

A Sample bot with examples of specific functionality for the legacy Actions SDK and DialogFLow (such as sending cards, lists etc.) is available [here](https://github.com/BotBuilderCommunity/botbuilder-community-dotnet/samples/Google%20Adapter%20Sample).
A Sample bot with examples of specific functionality for the legacy Actions SDK and DialogFLow (such as sending cards, lists etc.) is available [here](../../samples/Google%20Adapter%20Sample).

## Usage

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@

# Description

This is part of the [Bot Builder Community Extensions](https://github.com/botbuildercommunity) project which contains various pieces of middleware, recognizers and other components for use with the Bot Builder .NET SDK v4.
This is part of the [Bot Builder Community](https://github.com/botbuildercommunity) project which contains Bot Framework Components and other projects / packages for use with Bot Framework Composer and the Bot Builder .NET SDK v4.

The Infobip SMS adapter enables receiving and sending SMS messages. The Infobip SMS Adapter allows you to add an additional endpoint to your bot for receiving SMS messages. The Infobip endpoint can be used
in conjunction with other channels meaning, for example, you can have a bot exposed on out of the box channels such as Facebook and
Expand All @@ -34,10 +34,6 @@ Install into your project using the following command in the package manager;
PM> Install-Package Bot.Builder.Community.Adapters.Infobip.Sms
```

## Sample

Sample bot, showing examples of Infobip specific functionality is available [here](https://github.com/BotBuilderCommunity/botbuilder-community-dotnet/samples/Infobip%Sms%20Sample).

## Usage

- [Prerequisites](#prerequisites)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@

# Description

This is part of the [Bot Builder Community Extensions](https://github.com/botbuildercommunity) project which contains various pieces of middleware, recognizers and other components for use with the Bot Builder .NET SDK v4.
This is part of the [Bot Builder Community](https://github.com/botbuildercommunity) project which contains Bot Framework Components and other projects / packages for use with Bot Framework Composer and the Bot Builder .NET SDK v4.

The Infobip Viber adapter enables receiving and sending Viber messages. The Infobip Viber adapter allows you to add an additional endpoint to your bot for receiving Viber messages. The Infobip endpoint can be used in conjunction with other channels meaning, for example, you can have a bot exposed on out of the box channels such as Facebook and Teams, but also via an Infobip (as well as side by side with the Google / Twitter Adapters also available from the Bot Builder Community Project).

Expand All @@ -33,10 +33,6 @@ Install into your project using the following command in the package manager;
PM> Install-Package Bot.Builder.Community.Adapters.Infobip.Viber
```

## Sample

Sample bot, showing examples of Infobip specific functionality is available [here](https://github.com/BotBuilderCommunity/botbuilder-community-dotnet/tree/master/samples/Infobip%20Viber%20Sample).

## Usage

- [Prerequisites](#prerequisites)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@

# Description

This is part of the [Bot Builder Community Extensions](https://github.com/botbuildercommunity) project which contains various pieces of middleware, recognizers and other components for use with the Bot Builder .NET SDK v4.
This is part of the [Bot Builder Community](https://github.com/botbuildercommunity) project which contains Bot Framework Components and other projects / packages for use with Bot Framework Composer and the Bot Builder .NET SDK v4.

The Infobip Whatsapp adapter enables receiving and sending Whatsapp messages. The Infobip WhatsApp Adapter allows you to add an additional endpoint to your bot for receiving WhatsApp messages. The Infobip endpoint can be used
in conjunction with other channels meaning, for example, you can have a bot exposed on out of the box channels such as Facebook and
Expand Down Expand Up @@ -38,10 +38,6 @@ Install into your project using the following command in the package manager;
PM> Install-Package Bot.Builder.Community.Adapters.Infobip.WhatsApp
```

## Sample

Sample bot, showing examples of Infobip specific functionality is available [here](https://github.com/BotBuilderCommunity/botbuilder-community-dotnet/samples/Infobip%20WhatsApp%20Sample).

## Usage

- [Prerequisites](#prerequisites)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ This project is created by Ahmet Kocadoğan to help Bot Framework community for

# Description

This is part of the [Bot Builder Community Extensions](https://github.com/botbuildercommunity) project which contains various pieces of middleware, recognizers and other components for use with the Bot Builder .NET SDK v4.
This is part of the [Bot Builder Community](https://github.com/botbuildercommunity) project which contains Bot Framework Components and other projects / packages for use with Bot Framework Composer and the Bot Builder .NET SDK v4.

The MessageBird WhatsApp adapter enables receiving and sending WhatsApp messages. The MessageBird adapter allows you to add an additional endpoint to your bot for receiving WhatsApp messages. The MessageBird endpoint can be used in conjunction with other channels meaning, for example, you can have a bot exposed on out of the box channels such as Facebook and Teams, but also via an MessageBird (as well as side by side with the Google/Twitter adapters also available from the Bot Builder Community Project).

Expand All @@ -20,6 +20,9 @@ The adapter currently supports the following scenarios:
* Receive delivery reports
* Full incoming request from MessageBird is added to the incoming activity as ChannelData

### Sample

Basic sample bot available [here](../../samples/MessageBird%20Adapter%20Sample).

## Usage

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@

### Description

This is part of the [Bot Builder Community Extensions](https://github.com/garypretty/botbuilder-community) project which contains various pieces of middleware, recognizers and other components for use with the Bot Builder .NET SDK v4.
This is part of the [Bot Builder Community](https://github.com/garypretty/botbuilder-community) project which contains Bot Framework Components and other projects / packages for use with Bot Framework Composer and the Bot Builder .NET SDK v4.

The [RingCentral](https://www.ringcentral.com/) Engage adapter allows you to add an additional endpoint to your bot for [RingCentral Engage Digital Platform](https://www.ringcentral.com/digital-customer-engagement.html) integration. The RingCentral endpoint can be used in conjunction with other channels meaning, for example, you can have a bot exposed on out of the box channels such as Facebook and Teams, but also integrated as an [RingCentral Engage Digital Source SDK](https://support.ringcentral.com/s/article/RingCentral-Engage-Digital-Introduction?language=en_US) into RingCentral.

Expand Down Expand Up @@ -46,7 +46,7 @@ Install into your project using the following command in the package manager;

### Sample

Basic sample bot available [here](https://github.com/BotBuilderCommunity/botbuilder-community-dotnet/tree/master/samples/RingCentral%20Adapter%20Sample).
Basic sample bot available [here](../../samples/RingCentral%20Adapter%20Sample).

### Usage

Expand Down
4 changes: 4 additions & 0 deletions libraries/Bot.Builder.Community.Adapters.Twitter/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,10 @@ Use nuget to add the required dependencies

dotnet add package Bot.Builder.Community.Twitter.Adapter

### Sample

Basic sample bot available [here](../../samples/Twitter%20Adapter%20Sample).

## Configuration

Use the provided extensions to setup the adapter, middleware and hosted service in .NET Core
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,7 @@
<PackageReference Include="Microsoft.Bot.Builder.Integration.AspNet.Core" Version="$(Bot_Builder_Version)" />
<PackageReference Include="Microsoft.Net.Http.Headers" Version="2.1.1" />
<PackageReference Include="RestSharp" Version="106.10.2-alpha.0.8" />
<PackageReference Include="System.ComponentModel.Annotations" Version="5.0.0" />
</ItemGroup>

<ItemGroup>
Expand Down
4 changes: 2 additions & 2 deletions libraries/Bot.Builder.Community.Adapters.Zoom/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@

## Description

This is part of the [Bot Builder Community Extensions](https://github.com/botbuildercommunity) project which contains various pieces of middleware, recognizers and other components for use with the Bot Builder .NET SDK v4.
This is part of the [Bot Builder Community](https://github.com/botbuildercommunity) project which contains Bot Framework Components and other projects / packages for use with Bot Framework Composer and the Bot Builder .NET SDK v4.

The Zoom Adapter allows you to add an additional endpoint to your bot for Zoom apps. The Zoom endpoint can be used
in conjunction with other channels meaning, for example, you can have a bot exposed on out of the box channels such as Facebook and
Expand All @@ -34,7 +34,7 @@ Install into your project use the following command in the package manager.

## Sample

Sample bot, showing examples of Zoom specific functionality is available [here](https://github.com/BotBuilderCommunity/botbuilder-community-dotnet/samples/Zoom%20Adapter%20Sample).
Sample bots showing examples of Zoom specific functionality are available [here](../../samples/Zoom%20Adapter%20Sample) and [here](../../samples/Teams%20Zoom%20Sample).

## Usage

Expand Down
Original file line number Diff line number Diff line change
@@ -1,11 +1,20 @@
namespace Bot.Builder.Community.Adapters.Zoom
using System.ComponentModel.DataAnnotations;

namespace Bot.Builder.Community.Adapters.Zoom
{
public class ZoomAdapterOptions
{
public bool ValidateIncomingZoomRequests { get; set; } = true;

[Required]
public string ClientSecret { get; set; }

[Required]
public string ClientId { get; set; }

[Required]
public string BotJid { get; set; }

public string VerificationToken { get; set; }
}
}
Loading

0 comments on commit 1349229

Please sign in to comment.