Update to version 6.0.0 #70
Merged
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.
[ 6.0.0 ] - 2024-12-09
In this release we updated the library to use the latest version of the Infobip API. We also updated the library to use the latest version of the Symfony components. Minimum Symfony
version required is 7.0.
🎉 NEW Major Version of
infobip-api-php-client
.Added
Changed
Dependencies
Model changes
SmsTextualMessage
andSmsBinaryMessage
, providing a unified structure for SMS messaging.SmsMessage
to define the message content.This supports both textual and binary messages, which can be created using SmsTextContent or SmsBinaryContent, respectively.
SmsAdvancedTextualRequest
andSmsAdvancedBinaryRequest
with the new SmsRequest class.sendSmsMessages
instead of thesendSmsMessage
andsendBinarySmsMessage
functions.applicationId
field has been removed and replaced with theplatform
field, as encapsulates platform fields and reflects the current state of the endpoint.In addition to that, a new required
callsConfigurationId
field has been added.SmsDeliveryTimeWindow
,MmsDeliveryTimeWindow
,ViberDeliveryTimeWindow
,CallRoutingAllowedTimeWindow
,CallsDeliveryTimeWindow
,SmsDeliveryTimeWindow
,CallsTimeWindow
) in favor of a unified class: DeliveryTimeWindowSmsDeliveryTimeFrom
,SmsDeliveryTimeTo
,MmsDeliveryTime
,ViberDeliveryTime
,CallsTimeWindowPoint
,WebRtcTimeOfDay
,CallRoutingAllowedTimeFrom
,CallRoutingAllowedTimeTo
,WebRtcTimeOfDay
) in favor of a unified class: DeliveryTimeMessagesApiUrlOptions
,ViberUrlOptions
,WhatsAppUrlOptions
) in favor of a unified class: UrlOptionsViberPlatform
,MessagesApiPlatform
) in favor of a unified class: PlatformSmsDeliveryDay
,MmsDeliveryDay
,CallsDeliveryDay
,CallRoutingAllowedDay
) in favor of a unified class: DeliveryDayViberValidityPeriod
,MessagesApiValidityPeriod
) in favor of a unified class: ValidityPeriodViberValidityPeriodTimeUnit
,MessagesApiValidityPeriodTimeUnit
) in favor of a unified class: ValidityPeriodTimeUnitModelInterface
since it's no longer needed and not used in serialization anymore.Fixed