You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should [findTwicket()|https://github.com/zendesk/zendesk_api_client_php/blob/master/src/Zendesk/API/Resources/Core/Tickets.php#L116] be rename to be a bit more descriptive to something like findTwitterTicketStatus() as it's not obvious to what it's doing. Or put in an @see https://developer.zendesk.com/rest_api/docs/core/twitter_channel#getting-twicket-status.
At a glance it looks like there is a spelling mistake for this and it should be findTicket but after reading the comments I understood what it was doing. However, when comparing that to the Zendesk API documentation this is getting the [statuses|https://developer.zendesk.com/rest_api/docs/core/twitter_channel#getting-twicket-status.]
I also couldn't find an test coverage for this method. I would be happy to look into making the change, but wanted to see if this is something that would be of interest.
The text was updated successfully, but these errors were encountered:
Should [findTwicket()|https://github.com/zendesk/zendesk_api_client_php/blob/master/src/Zendesk/API/Resources/Core/Tickets.php#L116] be rename to be a bit more descriptive to something like findTwitterTicketStatus() as it's not obvious to what it's doing. Or put in an
@see https://developer.zendesk.com/rest_api/docs/core/twitter_channel#getting-twicket-status
.At a glance it looks like there is a spelling mistake for this and it should be
findTicket
but after reading the comments I understood what it was doing. However, when comparing that to the Zendesk API documentation this is getting the [statuses|https://developer.zendesk.com/rest_api/docs/core/twitter_channel#getting-twicket-status.]I also couldn't find an test coverage for this method. I would be happy to look into making the change, but wanted to see if this is something that would be of interest.
The text was updated successfully, but these errors were encountered: