Why remove functionality without deprecation in minor upgrade?
dorukgezici opened this issue · comments
Issue Summary
Since there are lots of companies that depend on Twilio for their daily operations, I find it unacceptable to remove a feature without deprecation in a minor upgrade, and without any replacement guidelines.
Here is the quote from 8.2.0:
Remove start_date, end_date and state query parameters from list operation on Conversations resource (breaking change)
Well, our software depends on the state filtering and sorting. What should we utilize to achieve the same functionality without being absurdly inefficient? Why were these parameters removed in such an unprofessional way?
I am ofc aware I can just keep using 8.1.0, and I will do that for now. But as a Twilio partner I felt my trust was violated and had to share this.
Technical details:
- twilio-python version: 8.2.0
@dorukgezici We will check with the Conversation team for the alternatives.
Hi @dorukgezici
Team is working on introducing the feature. As of now you can use previous version.
Ticket has been created, you might not be able to see it.
For book keeping Feature is being worked on
https://issues.corp.twilio.com/browse/CONCORE-1945
Thank you, I see they are added back with the latest release. So I'm closing this issue and upgrading my version.