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.

2.3.10

• PR #189 resolves a regression that caused php exceptions when embedded entities were present but empty

2.3.9

• PR #185 resolves an issue with the date format used when filtering Customers or Conversations

2.3.8

• PR #180 resolves #178 by preventing the hydration of empty objects when empty embedded collections were provided by the API
• PR #181 adds getCorrelationId() as an alias for getLogRef() so it's more clear how to provide the ID when contacting Help Scout
• PR #182 offers more clear direction on which scenarios can throw validation exceptions as well as more clear communication on how to obtain specifics on validation failures

2.3.7

Thanks to @matt-allan for submitting issue #175 and creating PR #176 to resolve it. There was an issue where the API response format changed and we were improperly assuming that HalDocument _embedded properties were only arrays and this was causing issues.

2.3.6

• Thanks to @dodedodo33 who submitted PR #173 resolving #172 where there was an issue with the request body that was being sent to the Help Scout API preventing users from using the SDK from running webhooks.

2.3.5

• PR #171 expands the available shorthand types for Customers. You can now use these methods with strings and the SDK will build the underlying objects:
  • $customer->addChatHandle('helpscout', 'aim')
  • $customer->addSocialProfile('helpscout', 'twitter')
  • $customer->addPhone('14235554837')
  • $customer->addWebsite('https://helpscout.com')

2.3.4

• PR #167 resolves #163 - user is now correctly populated with the expected id of the user when creating a new Conversation
• PR #165 adds new shorthand syntax for adding an Email to a Customer - $customer->addEmail($emailAddress, 'work')

2.3.3

• Thanks again to @wking-io for PR #162 which resolves #161 where in a certain scenario $customer->getEmails() was incorrectly returning emails as a collection of strings rather than Emails

2.3.2

• Thanks to @wking-io for contributing PR #158 which added the webUrl attribute to the extract attributes for an Attachment
• Also thanks to @wking-io, PR #159 adds a getType() to help determine what type the existing thread is
• We've expanded on this functionality in PR #160 and now providing threads when hydrating a Conversation will now type each Thread to CustomerThread, PhoneThread, NoteThread, etc. We only type thread types that can be created through the API. Any system-based or unknown thread types will not be typed