Skip to content

Commit

Permalink
docs: update v7.0.0 migration guides with latest breaking changes
Browse files Browse the repository at this point in the history
  • Loading branch information
Tr00d committed Mar 8, 2024
1 parent 2494760 commit f09a93c
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 1 deletion.
13 changes: 13 additions & 0 deletions MIGRATION_v7.0.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -148,3 +148,16 @@ is actually nullable.

As defined in the [specs](https://developer.vonage.com/en/voice/voice-api/ncco-reference#conversation),
the `Conversation` action doesn't have an `EventUrl` or an `EventMethod`.

## Make `From` mandatory in VerifyV2 WhatsApp workflow

The `From` property used to be optional - it is now mandatory.

```csharp
// Using v6.X.X
var workflow = WhatsAppWorkflow.Parse(ValidToNumber);
var workflow = WhatsAppWorkflow.Parse(ValidToNumber, ValidFromNumber);

// Using v7.X.X and above
var workflow = WhatsAppWorkflow.Parse(ValidToNumber, ValidFromNumber);
```
4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ If you would prefer to run directly from source:

#### Upgrading from v6.x.x to v7.0.0

Changes in version 7.0.0
Please see the dedicated [migration guide](MIGRATION_v7.0.0.md).

* Everything flagged with an `Obsolete` annotation will be removed
* Synchronous methods - [Pull Request](https://github.com/Vonage/vonage-dotnet-sdk/pull/549): So far, a lot of
Expand Down Expand Up @@ -104,6 +104,8 @@ Changes in version 7.0.0
* Make StartTime nullable on Answered Webhook - [link](https://github.com/Vonage/vonage-dotnet-sdk/issues/569).
* Remove `EventUrl` and `EventMethod` from `ConversationAction` to comply with
the [documentation](https://developer.vonage.com/en/voice/voice-api/ncco-reference#conversation).
* `From` is now mandatory in VerifyV2 WhatsApp
workflow - [Pull Request](https://github.com/Vonage/vonage-dotnet-sdk/pull/572)

#### Upgrading from v5.x.x to v6.0.0

Expand Down

0 comments on commit f09a93c

Please sign in to comment.