This repository was archived by the owner on Apr 12, 2023. It is now read-only.
Update dependency com.nexmo:client to v4.3.1 #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.0.1
->4.3.1
By merging this PR, the issue #1 will be automatically resolved and closed:
Release Notes
Nexmo/nexmo-java
v4.3.1
Fixed
v4.3.0
Added
NotifyAction
for use inNCCO
.Fixed
v4.2.1
Fixed
messages
.v4.2.0
Added
StreamAction
,AdvancedInsightRequest
,StandardInsightRequest
, andBasicInsightRequest
.Fixed
AbstractMethod
will force UTF-8 charset for requests usingStringEntity
.v4.1.0
Added
builder
methods toAction
classes to reduce some of the verbosity around using them. You can now doTalkAction action = TalkAction.builder("Hello World!").build();
instead of justTalkAction action = new TalkAction.Builder("Hello World).build();
.builder
methods toNexmoClient
to reduce some of the verbosity around instantiating the client.ncco
property to theCall
object for use in theVoiceClient.createCall
method. You can now send anNcco
directly to the API instead of defining ananswer_url
.