Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Deprecating Customer's Chat in favor of ChatHandle #102
I'd like to get some feedback on whether this is a good idea and/or if we should either toss it or tackle it differently.
Currently we use the terminology "chat" and "chats" for Customers. This can be a bit confusing because it's really a "chat handle", not any kind of conversation. If we add Chat reports or any other chat-related functionality it could create confusion for SDK users. Since we built the SDK, the api has been updated to use the terminology "chat handle".
To maintain backwards compatibility and adjust terminology to be consistent and more descriptive here's what I'm proposing with this PR:
What I don't like about this solution is having so much deprecation. But I like the naming improvement over the deprecation especially considering we have other aspects of the product/business where "Chat" refers to something completely different that may eventually be added to the API/SDK, especially from a reporting perspective.
We're still early in SDK adoption so deprecating now would have much lower impact than later. This PR is related to #100
What are your thoughts?