-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat!: make Twilio not singleton #675
Conversation
* feat: twilio implements twilioapi, changed usage examples * feat: change initialization of all tests (#3) * refactor: moved static block in twilio.java (#5) * refactor: changed this to static methods (#5) * feat: twilio class and interface final (#1 #5) * refactor: change synchronized back to original version (#3)
docs: adds essence to repo report (#2)
test: adds additional RequestValidator test cases
Is there a reason this pull request was closed? Allowing the Twilio client to be an object instead of static singleton makes it easier to mock and manage initialization. In particular, trying to create a reusable object by using the |
This PR was made as a school project and when after we submitted it, we did not receive any feedback or anything for like 8 months before I closed it. If you want to re-open it and continue the work that we started you are more than welcome to do it. We won't be doing anything more to this |
Fixes #650
Major version update.
Twilio class is no longer static singleton. Make it possible to have multiple instances of Twilio within the same program. Implement new TwilioApi.
Also update tests and example code.
Add few testcases to RequestValidatorTest.java as per issue #645
Checklist