Releases: helpscout/helpscout-api-php
Releases · helpscout/helpscout-api-php
2.7.0
3.1.0
2.6.0
3.0.1
3.0.0
With this release we're targeting improving the developer experience to make the SDK easier to work with. There's no new API interaction being added.
- [Breaking Change] PHP 7.1 has reached end of life and 7.2 is receiving security updates only, so v3 now requires PHP 7.3 (see #216). PHPDoc tags have been removed in favor of strongly typed parameters. Any classes that extend the SDK may require updating.
- [Breaking Change] All filter method names have changed and will need to be updated (see PRs #224, #225 and #226). Filter object's method names were causing some confusion. The code snippet
(new ConversationFilter())->withMailbox(40323)
can give the impression that we're eager loading mailbox40323
alongside the conversations, but it'll actually list the conversations in that mailbox. To make this more clear, we've eliminated thewith*()
verbiage for filters in favor of more specific verbiage likeinMailbox(2)
,modifiedSince(Carbon::now()->subDay())
andhasTag('trial-customer')
.
Refactored filter objects to use more clear terminology. - [Breaking Change] An
HelpScout\Api\Exception\AuthenticationException
is now thrown when the API responds with a 401. Previously this threw aGuzzleHttp\Exception\RequestException
, so if you are catching that exception to refresh your token, you'll need to update your code base. (see #212) - [Breaking Change]
HelpScout\Api\Customers\Entry\Chat
has been removed completely in place ofHelpScout\Api\Customers\Entry\ChatHandle
. This was previously deprecated in v2. (see #229, #100, #102) - New
isAssigned
method has been added toHelpScout\Api\Conversations\Threads\Thread.php
to help reduct additional logic when determining if a given Thread is assigned.(See #230)
2.5.0
1.9.6
2.4.1
2.4.0
- PR #191 fulfills #174 by adding the ability to list teams and their members
- PR #192 fulfills #183 by adding the ability to specify a status when creating Note or Reply threads
- PR #193 fulfills #179 by hydrating the first phone number for a Customer. We were already sending any other Customer fields alongside the Conversation creation.